hmm, they would all remain in the distribution, they would just not be loaded
by default.
the patch-author would have to load libraries explicitly, which would make it
(hopefully) more compatible with other distributions of Pd.
not exactly true, precisely the loading library from within the patch is exactly the less compatible feature between pd's versions, if ever it really works for good in one version all i know that really works is with -lib ...
most modern programming languages do not implicitly include 3rd (or even 1st)
party libraries (even though they are included in the standard distro); see java, perl,...
it was perfectly perl-like when obkect were left in extra and didn't need explicit loading..
xiaoo, sevy
ydegoyon@free.fr wrote:
hmm, they would all remain in the distribution, they would just not be loaded
by default.
the patch-author would have to load libraries explicitly, which would make it
(hopefully) more compatible with other distributions of Pd.
not exactly true, precisely the loading library from within the patch is exactly the less compatible feature between pd's versions, if ever it really works for good in one version all i know that really works is with -lib ...
hmm, well. you know, this is all because of nameclashes. if there weren't any, then there would be no need for Pd-extended organizing objects in a directory-structure, and everything would be flat and flurry.
most modern programming languages do not implicitly include 3rd (or even 1st)
party libraries (even though they are included in the standard distro); see java, perl,...
it was perfectly perl-like when obkect were left in extra and didn't need explicit loading..
i'm not a big perl-programmer, but they are using a lot :: magic for loading objects from Modules. isn't this comparable?
fgkasdr IOhannes
-
IOhannes m zmoelnig -
ydegoyon＠free.fr