On Sun, Jul 18, 2004 at 07:11:51PM -0400, Hans-Christoph Steiner wrote:
Part of putting all of the code into a central repository and also compiling all of the contributed objects as individual files allows us to eliminate such conflicts.
how so? if below is implemented:
implementing a (selectable) namespace for externals was one of the things that was discussed at the lad2conf in may
it seems it would be much easier if libraries were monolithic, containing all the objects in one file, so you could for example:
pd -lib maxlib:ml
and then use [ml:prepend] in your patch, if you send it to smoeone else and a "ml:" namespace is not found it will look in the global namespace. having as seperate files would much more difficult, unless you propose to change to the code of every external to hardcode a namespace identifier in?
guess the key would be adding optional namespace-mapping while having it not confuse earlier versions of pd, perhaps throwing the name of the preferred library somewhere after the ; ...