[aspectc-user] Puma.

[Robert Scott]

Hi,

I know some of these questions have come up recently, but I'd really like to 
know what the status of libpuma is.

While aspectc++ seems to be the 'product', libpuma itself is of far more use 
to me personally, and it seems rather neglected. I've been trying to piece 
together how things work with a combination of the sparse doxygen docs and a 
paper from 2001, since when the API seems to have changed greatly.

While of course I could delve into the source to see how things are done, 
that's made more difficult by the fact that it's partially written in a 
strange metalanguage.

The sort of thing I'm trying to figure out at the moment is how to get a 
classdb for a whole project or set of files, now that 
CClassDatabase::Expand() has been abolished.

So, what I'm asking is whether libpuma is going to remain a kind of internal 
utility library for aspectc++ or whether it's going to become more accessible 
& useful for outside projects. Because it seems a bit of a shame at the 
moment as it looks incredibly useful and competent.


robert.


p.s. (don't you hate it when people stick on unrelated p.s.'s?) To be able to 
compile against libpuma, I had to modify the headers to prove empty functions 
( '{}' ) for the virtuals Unit::~Unit(), Unit::name() and Unit::print(). 
Otherwise it wouldn't link. Is this normal?