hm.. only now, i see that overriding built-ins seems to be intentional. when starting pd with loading zexy, i get:
warning: class 'pack' overwritten; old one renamed 'pack_aliased' warning: class 'unpack' overwritten; old one renamed 'unpack_aliased'
and pd's built-in [pack] can be instantiated with [pack_aliased]
?????????
roman
On Tue, 2008-11-04 at 21:42 +0100, Roman Haefeli wrote:
hi all, hi IOhannes
after having installed pd 0.42.0test5, i assumed to have discovered a behaviour change of [unpack] and [pack], until i noticed:
a) zexy comes with its own version of [pack] and [unpack]. why are they called the same? i really don't get that.
b) in pd 0.42.0test5 they seem to override the built-in classes. is this a bug? if yes, pd's or zexy's?
c) the zexy versions can explicitly be called by using the 'zexy/' prefix. how is that possible, although zexy was compiled as multi class library? is that _the_ solution to have multiclass libs and separate namespaces at the same time?
it's definitely not backwards compatibility safe to replace all built-in [pack]/[unpack] by the zexy versions, since the zexy versions reads the 'f' and 's' literally and thus some patches produce lots of errors (due to inlets receiving 'f' instead of '0', for instance).
roman
___________________________________________________________ Der frhe Vogel fngt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de