13:28:45Bikewell, i'm still staring at the analyzer code for it, but i can maybe just figure it out
13:29:06Bikeif i want to use both the analyzer sif and the other sifs i guess i'll have to figure out how to correlate the names, since they work differently between them
13:29:13Bikenamespaces are separated or something in the scraper sifs
13:36:10drmeisterAre the namespaces not available in these new sif files?
13:39:33Bikewell, i think they are, just not in the same way
13:40:03Bikei'd have to use the STAMP-KEY, which is "gctools::GCVector_moveable<core::T_O *>" for example
13:42:19drmeisterAre you talking about correlating names from the scraper to the ones from the static analyzer?
13:42:55drmeisterIf so I'd say don't bother. The static analyzer gives a more complete view of the classes than you get from scraping the LISP_CLASS macros.
13:43:53drmeisterYou will need to correlate names from one static analyzer generated sif to another - but they will be identical.
13:45:34Bikewell, i was thinking of the stuff we were talking about where was verify that the info from both matches