On Mon, 2009-02-16 at 22:58 +0100, Frank Barknecht wrote:

from what i have understood, it is not cyclone's ability to replace built-ins, but it is a so called new feature of pd 0.42. the same happens also with zexy's [pack] and [unpack] and many others.

why is that so cool? i personally find it _very much_ confusing, that you cannot be sure anymore to use only pd-vanilla classes, when libraries are loaded. this new feature makes it impossible to stick with only-vanilla classes in one patch, where another one in the same instance of pd loads some libs. for me, the vanilla classes were some last 'safe' ressort, which is now polluted and messy, and i have to rely on thirdparty authors, and i need to trust them, that they write their externals compatible to the internals, so that my patches don't break. shouldn't the core library considered to be holy and untouchable, at least this one?

then again, as you say, this new features introduces _another_ difference between pd-extended and vanilla: overriding internal classes works only with libs and not with single-class-per-file collections.

why keeping backwards compabitility (which is the mentioned reason, why this new feature was introduced) on _any_ cost, even on cost of breaking patches and introducing new incompatibilities?

i am confused / confused / confused.....

roman