[PD] zexy aliasing policy

IOhannes m zmoelnig zmoelnig at iem.at
Mon Sep 19 15:39:14 CEST 2011

Hash: SHA1

On 2011-09-19 13:00, Jamie Bullock wrote:
> Hi IOhannes, list,
> Can you tell me if there is any policy about zexy aliasing internal objects? Mainly I want to know if it is your intention to maintain compatibility between builtins and zexy objects with the same name.

there are 2 cases here:
- - "zexy aliasing internal objects" applies (afaik), only to [pack] and
[unpack]; the policy is, that they ought to be compatible, but enhanced
versions of the original objects.
since in fact they are not, the shadowing of the built-in objects is
currently disabled, and you can only access these objects via
[zexy/pack] resp [zexy/unpack])

- - "internal objects aliasing zexy": this is more likely ([abs~] and
[wrap] come to my mind); the policy here is, to keep the old zexy
behaviour as long as this "enhances" (aka "adds to") the original behaviour.
if the internal object had an added feature, i would most likely add
this feature to the zey object (though this never happened, afair).
if the internal object breaks compatibility, i will most likely keep the
original zexy behaviour (unless the break is indeed a bugfix); afair,
this has not happened so far.

Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3636 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20110919/51b4d995/attachment.bin>

More information about the Pd-list mailing list