On Sun, 13 Feb 2011, Jonathan Wilkes wrote:
As well as in svn, where, for example, list-abs is in the abstractions
folder, but there are plenty of libraries in "externals" that are made
up only of abstractions.
That might because it's forbidden for any externals to be in the
abstractions folder. I once tried to include 1 % of C code in an
abstractions library I had put in abstractions/ , and was told I had to
move it out. Preventively, people can put abstractions libraries in
externals/ so that they never have to move them.
Does that seem like an accurate hypothesis ?
What else would be a reason to put those libraries in externals/ ?
I say that even though at the implementation level, abstractions
aren't classes, for the user, it works like a class. Also there are
many externals that don't include abstractions but are nonetheless
compatible with Pd vanilla.
What part of the text are you referring to, in particular ?
The last sentence states that list-abs "doesn't require any externals so
that it is compatible with vanilla Pd as well".
Yeah, that's nonsense. Pd-vanilla is the origin of the <m_pd.h> interface
for making externals.
The idea of Vanilla-without-externals is probably most useful to ZenGarden
users, who can't compile any existing externals, because ZenGarden was
designed to be incompatible with Pd-Vanilla. It is because of this
incompatibility, that Zengarden users are led to excessively focus on
what's compatible with Vanilla-without-Externals, because that's all that
the ZenGarden project aims to support.
Just another hypothesis. What do you think ?
_______________________________________________________________________
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
_______________________________________________
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
