On Fri 08 Sep, Eric Roode wrote: > Does anyone EVER use chomp() except shortly after reading a line > of input from a stream? No? > Yes > Perhaps $/ and $\ should become per-filehandle variables, and > there should be some way to set autochomp-on-read per filehandle, > and auto-newline-on-output per filehandle. I can see a small benefit for autochomp-on-read but none whatsoever for auto-newline-on-output (even if you could decide when to send it). Richard -- [EMAIL PROTECTED]
- 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