Re: s/// in string context should return the string

2003-11-25 Thread Piers Cawley
Jonathan Scott Duff [EMAIL PROTECTED] writes: On Wed, Nov 19, 2003 at 08:23:30PM +, Smylers wrote: This, however, is irritating: my @new = map { s:e/$pattern/$replacement/; $_ } @old; I forget the C; $_ far more often than I like to admit and end up with an array of integers

Re: s/// in string context should return the string

2003-11-25 Thread Mark J. Reed
On 2003-11-25 at 18:17:04, Piers Cawley wrote: aString replace: aPattern with: aString. aString replaceAll: aPattern with: aString. Stop! Stop that at once! No small talk; we're here for serious discussions! :) Except... the second argument isn't strictly a string because it's

Re: s/// in string context should return the string

2003-11-25 Thread Piers Cawley
Mark J. Reed [EMAIL PROTECTED] writes: On 2003-11-25 at 18:17:04, Piers Cawley wrote: aString replace: aPattern with: aString. aString replaceAll: aPattern with: aString. Stop! Stop that at once! No small talk; we're here for serious discussions! :) Except... the second

Re: s/// in string context should return the string

2003-11-20 Thread Smylers
Piers Cawley writes: Stéphane Payrard [EMAIL PROTECTED] writes: s/// in string context should return the string after substituion. Surely it should return the string after substitution, but with an appropriate 'but true' or 'but false' property depending on whether anything

Re: s/// in string context should return the string

2003-11-20 Thread Jonathan Scott Duff
On Wed, Nov 19, 2003 at 08:23:30PM +, Smylers wrote: This, however, is irritating: my @new = map { s:e/$pattern/$replacement/; $_ } @old; I forget the C; $_ far more often than I like to admit and end up with an array of integers instead of modified strings. That one gets me every

Re: s/// in string context should return the string

2003-11-20 Thread Luke Palmer
Smylers writes: Piers Cawley writes: Stphane Payrard [EMAIL PROTECTED] writes: s/// in string context should return the string after substituion. Surely it should return the string after substitution, but with an appropriate 'but true' or 'but false' property depending

Re: s/// in string context should return the string

2003-11-19 Thread Piers Cawley
Stéphane Payrard [EMAIL PROTECTED] writes: s/// in string context should return the string after substituion. It seems obvious to me but I mention it because I can't find it in the apocalypses. Surely it should return the string after substitution, but with an appropriate 'but true

Re: [perl] RE: s/// in string context should return the string

2003-11-19 Thread Piers Cawley
Joe Gottman [EMAIL PROTECTED] writes: - Original Message - From: Austin Hastings [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Tuesday, November 18, 2003 3:04 PM Subject: [perl] RE: s/// in string context should return the string As a Bvalue where possible, so

RE: [perl] RE: s/// in string context should return the string

2003-11-19 Thread Austin Hastings
-Original Message- From: Joe Gottman [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 18, 2003 9:58 PM To: Perl6 Subject: Re: [perl] RE: s/// in string context should return the string - Original Message - From: Austin Hastings [EMAIL PROTECTED] To: [EMAIL PROTECTED

Re: [perl] RE: s/// in string context should return the string

2003-11-19 Thread Simon Cozens
[EMAIL PROTECTED] (Larry Wall) writes: Sigh. There's no =~ operator in Perl 6. How should we go about bringing A3 up to match current reality? It is, after all, over two years old now. -- End July 2001 - Alpha release for demonstration at TPC

Re: [perl] RE: s/// in string context should return the string

2003-11-19 Thread Jonathan Scott Duff
On Wed, Nov 19, 2003 at 06:17:33PM +, Simon Cozens wrote: [EMAIL PROTECTED] (Larry Wall) writes: Sigh. There's no =~ operator in Perl 6. How should we go about bringing A3 up to match current reality? It is, after all, over two years old now. Isn't Allison the maintainer? Just prod

Re: [perl] RE: s/// in string context should return the string

2003-11-19 Thread Allison Randal
Simon wrote: How should we go about bringing A3 up to match current reality? It is, after all, over two years old now. We talked about this today. Our current thought is to retroactively write the Synopses and keep those up-to-date (with notes in the outdated parts of the A's and E's pointing

Re: [perl] RE: s/// in string context should return the string

2003-11-19 Thread Simon Cozens
[EMAIL PROTECTED] (Allison Randal) writes: We talked about this today. Our current thought is to retroactively write the Synopses and keep those up-to-date (with notes in the outdated parts of the A's and E's pointing to the relevant section of the S's). To be honest, I don't care how it's

s/// in string context should return the string

2003-11-18 Thread Stéphane Payrard
s/// in string context should return the string after substituion. It seems obvious to me but I mention it because I can't find it in the apocalypses. -- stef

RE: s/// in string context should return the string

2003-11-18 Thread Austin Hastings
As a Bvalue where possible, so they can cascade and nest. =Austin -Original Message- From: Stephane Payrard [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 18, 2003 12:19 PM To: [EMAIL PROTECTED] Subject: s/// in string context should return the string s/// in string context

Re: [perl] RE: s/// in string context should return the string

2003-11-18 Thread Joe Gottman
- Original Message - From: Austin Hastings [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Tuesday, November 18, 2003 3:04 PM Subject: [perl] RE: s/// in string context should return the string As a Bvalue where possible, so they can cascade and nest. Excuse me. I