Using loading order will have similar problems whether you use the first loaded or the last loaded. And changing the order of precedence will have lots of unintended consequences.
Modern programming languages use namespaces (C++, Python, Java, SmallTalk, etc). Namespaces are a much more appropriate and proven way to deal with this issue. Its already working in Pd on a basic level, and most of what's needed for a full-fledged namespace system is already implemented.
.hc
On Sep 26, 2006, at 9:41 AM, Miller Puckette wrote:
Yes indeed. I'm thinking of automatically having new classes shadow old ones, so that anything in Pd could simpy be "externed" over. Not sure of all the long-term ramifications, but I like the idea.
cheers Miller
On Tue, Sep 26, 2006 at 08:30:44AM +0000, carmen wrote:
and that is the question: why do we necessarily need the fftw based fft-objects in plain pd and cannot use externals?
so the only drawback is see is: the objects are called [fftw~] instead of [fft~]; but lo and behold, i vaguely remembered krzysztof magic in cyclone, where a newly loaded class raises itself over an already existing class. while he is using it to overwrite objects from other externals (e.g. iemmatrix's [matrix~]), i don't see any reason why this should not work with internals.
et voila, does this not sound good?
sounds good. maybe there should be some official policy on the overloading of internals?
mfg.adsr IOhannes
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
------------------------------------------------------------------------
News is what people want to keep hidden and everything else is publicity. - Bill Moyers