Ok, got a method to spit out a large list of all the class names in my (partial) Pd-l2ork git build. I'm on Debian so I search all the class paths and create any *.pd_linux objects I find there.
849 classes total (including the built-ins). I haven't loaded gem, pdp and some others. Add to that the caveats below and the real total is probably well over 1000 classes.
A few points of interest: * I'm not even loading all the libraries for which I have binaries. This is because at least four of the binaries cause a crash when I try to load the respective lib. I'll give more details later when I inspect the problems, but they look like unmaintained libraries-- cxc and a few others which I believe still ship with Pd-extended, too.
* this includes proxy inlets as well. I'm not sure there's a way to tell the difference between them and "real" classes. * after about an hour of head-scratching over a segfault, I realized that I made the assumption that every class loaded has a symbolic name. This isn't true. Zexy has two classes, presumably proxy inlets, that don't have a c_name. I'm actually not sure how to report that in Pd. Ideally the user should be able to get a list of everything that's had a trip through class_new, even if the developer doesn't want the class to be loadable or potentially clash with some other class name.
-Jonathan
On Tuesday, July 8, 2014 3:09 AM, IOhannes m zmoelnig via Pd-dev pd-dev@lists.iem.at wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2014-07-08 01:29, Jonathan Wilkes via Pd-dev wrote:
But again, this won't tell you about classes that are _potentially_ loadable by Pd-l2ork/Pd-extended
or Pd(-vanilla) for that matter.
gasm,dr
IOhannes
_______________________________________________ Pd-dev mailing list Pd-dev@lists.iem.at http://lists.puredata.info/listinfo/pd-dev