On Fri, Sep 08, 2000 at 02:50:37AM +0000, Ed Mills wrote: > Shoot chop. and chomp. Unless you add unchop and unchomp. Parity issue. Like > a language with YES and no NO. > > Just kill then both. Although I'm rather fond of symmetry, it's not inherently good. Rather boring if overused. I admit to being a bit sentimental about chop, but I can't think of any exciting reasons to keep it. The parity reasoning, however strikes me as a bad idea/precedent. dha -- David H. Adler - <[EMAIL PROTECTED]> - http://www.panix.com/~dha/ Just Install Perl. - Chris Nandor
- RFC 195 (v1) Retire chop(). Perl6 RFC Librarian
- Re: RFC 195 (v1) Retire chop(). Michael G Schwern
- Re: RFC 195 (v1) Retire chop(). Tom Christiansen
- Re: RFC 195 (v1) Retire chop(). Michael G Schwern
- Re: RFC 195 (v1) Retire chop(). Damian Conway
- Re: RFC 195 (v1) Retire chop(). Bryan C . Warnock
- Re: RFC 195 (v1) Retire chop(). Nathan Wiger
- Re: RFC 195 (v1) Retire chop(). Casey R. Tweten
- Re: RFC 195 (v1) Retire chop(). Ed Mills
- Re: RFC 195 (v1) Retire chop(). Tom Christiansen
- Re: RFC 195 (v1) Retire chop(). David H. Adler
- Re: RFC 195 (v1) Retire chop(). Damian Conway
- Re: RFC 195 (v1) Retire chop(). Eric Roode
- Re: RFC 195 (v1) Retire chop(). Richard Proctor
- Re: RFC 195 (v1) Retire chop(). Chaim Frenkel
- Re: RFC 195 (v1) Retire chop(). Eric Roode
- -a and @F autospliting Chaim Frenkel