silenus-dionysus

Down to two now that otable is done. The remaining ones should also be quite simple.

This feature should be optional in case people don't want information leaking from their privately compiled drivers to some central source without their permission.

The stack objects I think should be relatively easy to add to the root set since the stack in the driver is for better or worse currently a global variable.

I actually haven't thought about this in a little while. I think the main problem is that there are a lot of cases where the driver uses svalues in ways...

This is a sketch of some code I have been working on that I need to start testing. It basically is a mixin class that will be inherited by svalue_t,...

#include #include #include #include class garbage_collectable { public: static void* operator new(std::size_t size) throw(std::bad_alloc); virtual std::list follow_set() = 0; void setMark(bool mark); bool getMark() const; virtual ~garbage_collectable(); private: bool mark_;...

Problem is this is actually C++14 code ;-)

I think need to test and debug it now then implement a rootsetfunction that encapsulates the various sources of variables in the checkmemory code.

Sorry have been looking at other things for the last week. I just got back to looking at this. I think for the most part testing the mixin code and...

Actually this might be a bit harder than i initially thought because of the fact that svalues are not allocated on the heap and I am not sure at present...