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
<[email protected]> 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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iQIcBAEBCAAGBQJTu5jUAAoJELZQGcR/ejb4JUgQAJQRe2pueqG5Nk9KA4jYnUEI
2lj/AYc+ePEjuvZr3QaXvhslJkz7pLdxzbSz20EpA4mAZ4vBySU88e3/h6My9rXR
k/HO3Rg8gWwnhfGvPQZjRLBHIW7LhX2EWWWBjm+FNoMRzYV4frUNSGUk5cEze+Y0
c8r4srbM2hIWjdOXAZdIIVIkwayWYKDFrW8bgTkoOTbGLz/L0x/9m1H3VzLYJQzM
E7ylkHArmwuDGxcHFVZdtZlHFUI71LldPErhBjs3V9ZNqE5pydA18U8+UAFLbA4Q
063O/+Ehb+vx3cWmMti+cosJgxikGTdMORoHfGfYdGbSOL/3bGEX+hNVDwLr9Sly
mOI8l8oXkAILQ0uA7hSj4lthl9YKlCQXCpu+KmC5IKUxsIFpndMfCZAE+4VgxwsE
NFACYwejuowYYYD0gZtiIEAhmtJ/rkJJNrLePPSGq0fO1OzDROqkfIRBnl7E/FQm
dpRUm0kc65pNCC6VmSNKyCOSs3un+KgMHU3pSHzJBZuKvzYB6JCI3NMQdPty6kb7
otfh/ZQjNnWXykpq6tm4XPlZ2snu+kVaFt5jxZL1SqQeZDKkENPlz9OzmD35kTJR
4BhP9cOQI0njNyGMCOx5EpUhh50ALry2yetdUv4kftljGtmyoXBdq2zu2Gz04Rco
4nxHnf37bcZW5P6afcHP
=cQVQ
-----END PGP SIGNATURE-----
_______________________________________________
Pd-dev mailing list
[email protected]
http://lists.puredata.info/listinfo/pd-dev
_______________________________________________
Pd-dev mailing list
[email protected]
http://lists.puredata.info/listinfo/pd-dev
