Enhancement #648
Updated by S. Wrede over 12 years ago
We don't even know if this is actually a problem, but some ideas could be to
* Wrap cl-bag code using embeddable common lisp to get a library usable in c++
* Use socket-based transport to efficiently couple cl-bag tools and the component to be introspected
* Wrap cl-bag code using embeddable common lisp to get a library usable in c++
* Use socket-based transport to efficiently couple cl-bag tools and the component to be introspected