Re: RFC 125 (v2) Components in the Perl Core Should Have Well-Defined APIs and Behavior

2000-10-06 Thread Philip Newton
On 5 Oct 2000, at 15:06, Dan Sugalski wrote: [about his Darned Big Pile of books] > I should actually RFC it--we could use a "recommended reading" RFC. Sounds good -- I'd welcome such a list. It's be a replacement for the very short perlbook and the list in perlfaq3. And quite a lot of good stu

Re: RFC 125 (v2) Components... Should Have... And Testing !!!

2000-10-06 Thread John van V
I'm an admin, perl saved my life... However, yesterday, some simple IO::Socket scripts failed to work on 5.6. I'm not addressing that here but my resulting thought is now that the distribution should only include such core components as are necessariy to define perl's behavior. Those should

Re: RFC 361 (v1) Simplifying split()

2000-10-06 Thread Sean M. Burke
At 12:37 AM 2000-10-06 -0400, you wrote: >> "PRL" == Perl6 RFC Librarian <[EMAIL PROTECTED]> writes: > >PRL> =item 2. Empty trailing fields are currently suppressed (although a >PRL> -1 as the third argument disables this). I suggest that empty trailing >PRL> fields be retained by default. >

Re: RFC 361 (v1) Simplifying split()

2000-10-06 Thread Tom Christiansen
The reason that this was done this way was for the common case of someone forgetting to chop an incoming line and then splitting on whitespace. while (<>) { @F = split; ... }

Re: RFC 361 (v1) Simplifying split()

2000-10-06 Thread John Porter
Sean M. Burke wrote: > > The current behavior makes trailing empty fields non-existent, and that's a > bizarre and nonintuitive thing to have be a default; Only to some people; and besides, it's well documented. > if your code relies on > them being removed, then remove them explicitly, withou

Re: RFC 361 (v1) Simplifying split()

2000-10-06 Thread Tom Christiansen
>Sean M. Burke wrote: >> >> The current behavior makes trailing empty fields non-existent, and that's a >> bizarre and nonintuitive thing to have be a default; >Only to some people; and besides, it's well documented. Well, Sean is right in that it is very bizarre to many people. I know that whe

RE: RFC 326 (v1) Symbols, symbols everywhere

2000-10-06 Thread Fisher Mark
Chain Frenkel writes: >DS> For the internals, though... > >DS> This would be very useful, and it's a feature I'd really like to implement. >DS> Basically you're asking for pre-computed, indirect, shared hash keys. This >DS> sounds like a Good Plan to me. > >Why precomputed? Any 'interned' string

Re: RFC 361 (v1) Simplifying split()

2000-10-06 Thread Chaim Frenkel
> "TC" == Tom Christiansen <[EMAIL PROTECTED]> writes: TC> The reason that this was done this way was for the common TC> case of someone forgetting to chop an incoming line and TC> then splitting on whitespace. TC> while (<>) { TC> @F = split; TC> ... TC> } Interesting. I t

Re: RFC 125 (v2) Components... Should Have... And Testing !!!

2000-10-06 Thread Jarkko Hietaniemi
> However, yesterday, some simple IO::Socket scripts failed to work on > 5.6. I'm not addressing that here but my resulting thought is now I hope you will be addressing them in the form of perlbug reports so that the problems in 5.6 will be recorded and sorted out. > Those should be kept short

Re: RFC 361 (v1) Simplifying split()

2000-10-06 Thread Jonathan Scott Duff
On Fri, Oct 06, 2000 at 11:59:31AM -0600, Sean M. Burke wrote: > The current behavior makes trailing empty fields non-existent, and that's a > bizarre and nonintuitive thing to have be a default; if your code relies on > them being removed, then remove them explicitly, without expecting split to >