Re: name for 3 PICK finally?

On Mar 6, 7:51 am, Andrew Haley <andre...@[EMAIL PROTECTED]
>
wrote:
> Firstly, 3 PICK isn't a separate idea from 2 PICK: in both cases it's
> a red flag to the reader that you're using the stack as an array.

Quite so ... the place where it is not using the stack as an array is
when pulling out the char address of the second of two string
descriptors, or similarly the second part of the second of some other
paired data item or the LSCell of the second of a pair of doubles on
the stack.

And of course in all those cases, which would not be uncommon when
synthesizing a dyadic operation involving tuples, in pulling out the
second part of a tuple in synthesizing a dyadic operations on cell-
pair items, 2OVER DROP is more descriptive. Indeed, its not unusual
when factoring for the DROP to hide inside the factor so that the
factor just takes the type of cell-pair being worked with as its
argument.

> Secondly, every reader is instantly going to know what 3 PICK does,
> and giving it a name makes the code harder to read, not easier.

Precisely why I prefer ``2pick'' to ``pluck''. For me, ``pluck''
should be a keystrike of a stringed instrument, whether its
synthesized at hand or sent over a midi channel.