>But Tom, that preserves all the white space both before and after the '!'! >Michael's goal is to eliminate the leading white space, although he didn<SNIP> >'!' bit. So I'm not sure how you'd have written that if you'd have done<SNIP> >specification. Yeah, ok. I still think ##### Your stuff that you write ##### goes nicely right here ##### If you want it to print ##### sans mungeing to fear is the nicest way to heredoc, where "#####" is some distinctive string. --tom
- Re: RFC 111 (v3) Here Docs Ter... Nathan Wiger
- Re: RFC 111 (v3) Here Docs Ter... Richard Proctor
- Re: RFC 111 (v3) Here Docs Ter... Michael G Schwern
- Re: RFC 111 (v3) Here Docs Ter... Richard Proctor
- Re: RFC 111 (v3) Here Docs Ter... Glenn Linderman
- Re: RFC 111 (v3) Here Docs Ter... Nathan Wiger
- Re: RFC 111 (v3) Here Docs Ter... Glenn Linderman
- Re: RFC 111 (v3) Here Docs Ter... Tom Christiansen
- Re: RFC 111 (v3) Here Docs Ter... Tom Christiansen
- Re: RFC 111 (v3) Here Docs Ter... Glenn Linderman
- Re: RFC 111 (v3) Here Docs Ter... Tom Christiansen
- Re: RFC 111 (v3) Here Docs Termina... Bart Lateur
- Re: RFC 111 (v3) Here Docs Terminators (Was Whitespace a... H . Merijn Brand
- Re: RFC 111 (v3) Here Docs Terminators (Was Whitespace a... Richard Proctor
- Re: RFC 111 (v3) Here Docs Terminators (Was Whitespace a... Eric Roode
- Re: RFC 111 (v3) Here Docs Terminators (Was Whitespace a... Eric Roode
- Re: RFC 111 (v3) Here Docs Terminators (Was Whitesp... Richard Proctor
- Re: RFC 111 (v3) Here Docs Terminators (Was Whitespace a... Richard Proctor
- Re: RFC 111 (v3) Here Docs Terminators (Was Whitespace a... Eric Roode
- Re: RFC 111 (v3) Here Docs Terminators (Was Whitespace a... Eric Roode