RE: RFC 288 (v1) First-Class CGI Support

2000-09-24 Thread Greg Boug
> > Parse the CGI context, returning CGI variables into %CGI > Which variables are you talking about? Everything you need is already in > %ENV, as I'm sure you're aware. Yeah, but its encoded... %CGI in an unencoded form would be a nice thing. :) > If you're talking about splitting up the query

RE: RFC 290 (v1) Remove -X

2000-09-24 Thread Greg Boug
> > Perl programmers happy with the -X syntax will need to get used to the > > lengthier replacement. > Blech. I certainly think that long functions are fine and dandy, but I'd > loathe the day that I'd have to give up my -X stuff. I *love* it. I'm a > shell-head! Many Perlers are. I would not cla

Re: IDEA: my() extensions and attribute declarations

2000-09-24 Thread Alan Gutierrez
On Wed, 20 Sep 2000, Nathan Wiger wrote: > Camel-3 shows some interesting hints of what's been proposed for my > declarations: > >my type $var :attribute = $value; > > And we all know that you can use my to declare a group of variables: > >my($x, $y, $z); > > Here's the issues: > >

Re: RFC 288 (v1) First-Class CGI Support

2000-09-24 Thread Nathan Wiger
> Perl is frequently used in CGI environments. It should be as easy to write > CGI programs with perl as it is to write commandline text filters. First off, good idea, I do like this. Critiques: > Parse the CGI context, returning CGI variables into %CGI Which variables are you talking about? E

Re: RFC 255 (v2) Fix iteration of nested hashes

2000-09-24 Thread Damian Conway
Dear all, Since no-one has put their hand up to take this RFC over, I am now intending to retract it. I simply don't have the time to try and find a solution to the many (valid) problems that have been pointed out. I would heartily encourage anyone who wants to take on this monster to steal what

Re: RFC 290 (v1) Remove -X

2000-09-24 Thread Nathan Wiger
> File tests (-r/-w/-x/...) made sense when Perl's shellness was an > attribute. Most new Perl programmers are not coming from a shell > programming background, and the -X syntax is opaque and bizarre. > It should be removed. > Perl programmers happy with the -X syntax will need to get used to t

Re: RFC 285 (v1) Lazy Input

2000-09-24 Thread Damian Conway
> =head1 IMPLEMENTATION > > Tricky. > > Perl needs to know about scalar context, list context, and "finite > list" context. Presumably, if I/O routines behave this way, user > subs should be able to behave this way as well. Might use the same > machinery as lazy subs.

RFC 290 (v1) Remove -X

2000-09-24 Thread Perl6 RFC Librarian
This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Remove -X =head1 VERSION Maintainer: Adam Turoff <[EMAIL PROTECTED]> Date: 24 Sep 2000 Mailing List: [EMAIL PROTECTED] Number: 290 Version: 1 Status: Developing =head1 ABSTRACT File tests (-r/

RFC 288 (v1) First-Class CGI Support

2000-09-24 Thread Perl6 RFC Librarian
This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE First-Class CGI Support =head1 VERSION Maintainer: Adam Turoff <[EMAIL PROTECTED]> Date: 24 Sep 2000 Mailing List: [EMAIL PROTECTED] Number: 288 Version: 1 Status: Developing =head1 ABSTRACT P

RFC 287 (v1) Improve Perl Persistance

2000-09-24 Thread Perl6 RFC Librarian
This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Improve Perl Persistance =head1 VERSION Maintainer: Adam Turoff <[EMAIL PROTECTED]> Date: 24 Sep 2000 Mailing List: [EMAIL PROTECTED] Number: 287 Version: 1 Status: Developing =head1 ABSTRACT

RFC 285 (v1) Lazy Input

2000-09-24 Thread Perl6 RFC Librarian
This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Lazy Input =head1 VERSION Maintainer: Adam Turoff <[EMAIL PROTECTED]> Date: 24 Sep 2000 Mailing List: [EMAIL PROTECTED] Number: 285 Version: 1 Status: Developing =head1 ABSTRACT Currently, fil

RFC 284 (v1) Change C<$SIG{__WARN__}> and C<$SIG{__DIE__}> to magic subs

2000-09-24 Thread Perl6 RFC Librarian
This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Change C<$SIG{__WARN__}> and C<$SIG{__DIE__}> to magic subs =head1 VERSION Maintainer: Simon Cozens <[EMAIL PROTECTED]> Date: 24 Sep 2000 Mailing List: [EMAIL PROTECTED] Number: 284 Version: 1 S

RFC 283 (v1) C in array context should return a histogram

2000-09-24 Thread Perl6 RFC Librarian
This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE C in array context should return a histogram =head1 VERSION Maintainer: Simon Cozens <[EMAIL PROTECTED]> Date: 24 Sep 2000 Mailing List: [EMAIL PROTECTED] Number: 283 Version: 1 Status: Developi

RFC 282 (v1) Open-ended slices

2000-09-24 Thread Perl6 RFC Librarian
This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Open-ended slices =head1 VERSION Maintainer: Simon Cozens <[EMAIL PROTECTED]> Date: 24 Sep 2000 Mailing List: [EMAIL PROTECTED] Number: 282 Version: 1 Status: Developing =head1 ABSTRACT The dr

RFC 280 (v1) Tweak POD's CEE

2000-09-24 Thread Perl6 RFC Librarian
This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Tweak POD's CEE =head1 VERSION Maintainer: Simon Cozens <[EMAIL PROTECTED]> Date: 24 Sep 2000 Mailing List: [EMAIL PROTECTED] Number: 280 Version: 1 Status: Developing =head1 ABSTRACT CEE is

Re: perl6storm #0050

2000-09-24 Thread Dave Storrs
On Sat, 23 Sep 2000, raptor wrote: > > On Thu, 21 Sep 2000, Tom Christiansen wrote: > > > > > =item perl6storm #0050 > > > > > > Radical notion: consider removing precedence. > > > Wrong precedence makes people miserable. > What if we have these 2 rules or no rules AND we can set manualy the >

Re: RFC 275 (v1) Add 'tristate' pragma to allow undef to take on NULL semantics

2000-09-24 Thread Nathan Wiger
Jeremy Howard wrote: > > Yes, that's nullirific! > > It would be good to make that clear in the RFC. :-) Will do. -Nate

Re: RFC 275 (v1) Add 'tristate' pragma to allow undef to take on NULL semantics

2000-09-24 Thread Jeremy Howard
Nathan Wiger wrote: > Jeremy Howard wrote: > > > > Can we have an isnull() function then, please. Otherwise there's no > > operation to test for nullness. > > > > PS: Nullness? Nullility? > <...> >use tristate; >$a = undef; >carp "\$a is null!" unless defined($a); > > That way, "de

RFC 278 (v1) Additions to 'use strict' to fix syntactic ambiguities

2000-09-24 Thread Perl6 RFC Librarian
This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Additions to 'use strict' to fix syntactic ambiguities =head1 VERSION Maintainer: Nathan Wiger <[EMAIL PROTECTED]> Date: 24 Sep 2000 Mailing List: [EMAIL PROTECTED] Number: 278 Version: 1

RFC 277 (v1) Eliminate unquoted barewords from Perl entirely

2000-09-24 Thread Perl6 RFC Librarian
This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Eliminate unquoted barewords from Perl entirely =head1 VERSION Maintainer: Nathan Wiger <[EMAIL PROTECTED]> Date: 24 Sep 2000 Mailing List: [EMAIL PROTECTED] Number: 277 Version: 1 Status: Devel

Re: RFC 271 (v1) Subroutines : Pre- and post- handlers for subroutines

2000-09-24 Thread Damian Conway
Thanks for the feedback Uri. Some specific points: > PRL>pre tax_payable_on { > PRL> $_[0] -= 20.00; # routinely underquote sales price > PRL>} > > i assume like normal subs, that changes the original argument in the > caller. Correct. Guess I'd

Re: RFC 259 (v2) Builtins : Make use of hashref context for garrulousbuiltins

2000-09-24 Thread Nathan Wiger
>> > 'dir' Home directory >> >> 'homedir' or 'home' are _much_ better for us sysadmins... > > Not if you sysadmins are familiar with the UNIX documentation, whence *all* > these names are taken! ;-) Well, I've always hated it, and most everyone I know does t

Re: RFC 259 (v2) Builtins : Make use of hashref context for garrulous builtins

2000-09-24 Thread Damian Conway
> > =item C/C > > > > 'blksize' Preferred block size for file system I/O > > 'blocks'Actual number of blocks allocated > > Either "blocks" and "blocksize", or "blks" and "blksize", I think What's there is what's been in perlfunc fo

Re: RFC 275 (v1) Add 'tristate' pragma to allow undef to take on NULL semantics

2000-09-24 Thread Nathan Wiger
Jeremy Howard wrote: > > Can we have an isnull() function then, please. Otherwise there's no > operation to test for nullness. > > PS: Nullness? Nullility? I've been thinking about how to test for nullirificity. The problem is that introducing an 'isnull' keyword without a 'null' keyword seems

Re: RFC 259 (v2) Builtins : Make use of hashref context for garrulous builtins

2000-09-24 Thread Nathan Wiger
Good idea, I'm going to nitpick a few names now... > =item C/C > > 'blksize' Preferred block size for file system I/O > 'blocks'Actual number of blocks allocated Either "blocks" and "blocksize", or "blks" and "blksize", I think > =item C > >

Re: Perl6Storm: Intent to RFC #0101

2000-09-24 Thread Nathan Wiger
Ariel Scolnicov wrote: > > > is_readable(file) is really -r(file) > > Has unpleasant syntax saying "is_readable". Should be like normal > English predicates. Get the idea you do. Is better even the Lisp -p > convention! > > What's wrong with doing it like I (and maybe a few others) speak

Re: Perl6Storm: Intent to RFC #0101

2000-09-24 Thread Ariel Scolnicov
Adam Turoff <[EMAIL PROTECTED]> writes: > I plan to offer a more formal RFC of this idea. > > Z. > > =item perl6storm #0101 > > Just like the "use english" pragma (the modern not-yet-written > version of "use English" module), make something for legible > fileops. > > is_readable(file) is

Re: RFC 275 (v1) Add 'tristate' pragma to allow undef to take on NULL semantics

2000-09-24 Thread Jeremy Howard
> =head1 TITLE > > Add 'tristate' pragma to allow undef to take on NULL semantics > <...> > > The C pragma allows for undef to take on the RDBMS concept of > C, in particular: > >1. Any math or string operation between a NULL and any other > value results in NULL > Any math or string or