Re: RFC 272 (v1) Arrays: transpose()

2000-09-24 Thread Jeremy Howard
[EMAIL PROTECTED] wrote: Jeremy Howard wrote: So where is mv(), you ask? If you use the 'reorder' syntax, but don't specify all of the dimensions in the list ref, then the remaining dimensions are added in order: That sounds good. I'd say why not also allow the mv syntax? It is

RFC 272 (v2) Arrays: transpose()

2000-09-24 Thread Perl6 RFC Librarian
This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Arrays: transpose() =head1 VERSION Maintainer: Jeremy Howard [EMAIL PROTECTED] Date: 22 Sep 2000 Last Modified: 24 Sep 2000 Mailing List: [EMAIL PROTECTED] Number: 272 Version: 2 Status:

Re: TAI and Unix epoch issues

2000-09-24 Thread Nathan Wiger
Nathan Wiger wrote: I think we should definitely maintain this in UTC, since this is how UNIX works natively. If we're standardizing on the UNIX epoch we should standardize on UTC clock as well. Blech. Now I'm not sure after re-reading the thread starting here:

RFC 152 (v2) Replace invocant in @_ with self() builtin

2000-09-24 Thread Perl6 RFC Librarian
This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Replace invocant in @_ with self() builtin =head1 VERSION Maintainer: Nathan Wiger [EMAIL PROTECTED] Date: 24 Aug 2000 Last Modified: 24 Sep 2000 Mailing List: [EMAIL PROTECTED] Number: 152

RFC 279 (v1) my() syntax extensions and attribute declarations

2000-09-24 Thread Perl6 RFC Librarian
This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE my() syntax extensions and attribute declarations =head1 VERSION Maintainer: Nathan Wiger [EMAIL PROTECTED] Date: 24 Sep 2000 Mailing List: [EMAIL PROTECTED] Number: 279 Version: 1 Status:

Re: Perlstorm #0040

2000-09-24 Thread Richard Proctor
On Sun 24 Sep, Hugo wrote: In [EMAIL PROTECTED], Richard Proctor writes : :TomCs perl storm has: : : Figure out way to do : : /$e1 $e2/ : : safely, where $e1 might have '(foo) \1' in it. : and $e2 might have '(bar) \1' in it. Those won't work. : :If e1 and e2 are qr// type

RFC 276 (v1) Localising Paren Counts in qr()s.

2000-09-24 Thread Perl6 RFC Librarian
This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Localising Paren Counts in qr()s. =head1 VERSION Maintainer: Richard Proctor [EMAIL PROTECTED] Date: 24 Sep 2000 Mailing List: [EMAIL PROTECTED] Number: 276 Version: 1 Status: Developing

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 Ctristate pragma allows for undef to take on the RDBMS concept of CNULL, in particular: 1. Any math or string operation between a NULL and any other value results in NULL Any math or string or

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 really

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, and

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

2000-09-24 Thread Damian Conway
=item Cstat/Clstat '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

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 too. And

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, "defined($a)" will

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: 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 precedence of

RFC 280 (v1) Tweak POD's CEltEgt

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 CEltEgt =head1 VERSION Maintainer: Simon Cozens [EMAIL PROTECTED] Date: 24 Sep 2000 Mailing List: [EMAIL PROTECTED] Number: 280 Version: 1 Status: Developing =head1 ABSTRACT

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

RFC 283 (v1) Ctr/// 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 Ctr/// 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:

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

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 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

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

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