On Mon 25 Sep, Perl6 RFC Librarian wrote:
> This and other RFCs are available on the web at
> http://dev.perl.org/rfc/
>
> =head1 TITLE
>
> First-Class CGI Support
>
> Maintainer: Adam Turoff <[EMAIL PROTECTED]>
>
> To make CGI programming easier, this option/pragma should:
>
> Turn on ta
On Mon, 25 Sep 2000, Nathan Wiger wrote:
> > I'd even go so far as to say that the current -X syntax should be
> > _extended_, to allow for multiple tests at once, maybe by way of a
> > leading caret (mnemonic "all"):
> >
> > -^rwx; # $_ is readable, writable and executable
> >
> >
> if ( all { $_->($file) } \&writable, \&directory ) { ...
Is that the PDL C?
With the superpositional C it would be:
if ( all(\&writable, \&directory)->($file) ) { ...
:-)
Hm. Maybe C, C, etc. could return objects
that equate to a filename *only* if the original predicate is t
> > > I'd even go so far as to say that the current -X syntax should be
> > > _extended_, to allow for multiple tests at once, maybe by way of a
> > > leading caret (mnemonic "all"):
> > >
> > > -^rwx; # $_ is readable, writable and executable
> > >
> > > ($s
Perl6 RFC Librarian wrote:
> =head1 ABSTRACT
>
> 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.
> is_re
"John L. Allen" wrote:
>
> The use of a caret was to prevent decimation of the user's namespace,
> vis:
>
> perl -e 'print -rwx $_'
> Can't call method "rwx" on an undefined value at -e line 1.
Yeah, but read the error - Perl's parsing that as:
[nwiger@matrix:~]$ perl -MO=Depar
On Sun, 24 Sep 2000, Nathan Wiger wrote:
> > Offer simple functions to set HTTP headers (e.g. content type, result codes)
> How about %HTTP, which is just flushed on the first line of output?
>use cgi;
>$HTTP{'Content-type'} = 'text/html';
>print "Hello!"; # flushes %HTTP first
> It sounds really stoopid to say C<$SIG{__WARN__}> on a machine which
> doesn't have signals.
Indeed. It is also worth noting that people on -flow have been hashing
out safe signals through a "use signal" pragma, which would remove %SIG
altogether.
> Instead, let's implement them as magic subr
On Mon, Sep 25, 2000 at 11:10:04AM -0700, Nathan Wiger wrote:
> Indeed. It is also worth noting that people on -flow have been hashing
> out safe signals through a "use signal" pragma, which would remove %SIG
> altogether.
Oh, well, OK. Then this RFC's necessary, dammit! :)
> I like it! But I'm
> "PRL" == Perl6 RFC Librarian <[EMAIL PROTECTED]> writes:
PRL> All of the other features offered by Lincoln Stein's CGI.pm
PRL> should remain, but should not be deeply integrated into Perl6.
PRL> Write a very small cgi.pm module that does as little as possible,
PRL> probably based o
On Sun, 24 Sep 2000 23:05:45 -0700, Nathan Wiger wrote:
>> 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
On Mon, 25 Sep 2000, Clayton Scott wrote:
> It:
> + stacks multiple tests quite cleanly without excess verbiage
>(if (-e && -T && -s && -x){...} gets a little tedious especially
>if you don't use $_)
> + introduces only 1 new keyword ("file" seems bad, but maybe not)
> + does not bre
> I'd even go so far as to say that the current -X syntax should be
> _extended_, to allow for multiple tests at once, maybe by way of a
> leading caret (mnemonic "all"):
>
> -^rwx; # $_ is readable, writable and executable
>
> ($size, $mod, $acc, $ichange) = -^sMAC;
In fact, yo
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Extensions to the perl debugger
=head1 VERSION
Maintainer: David Storrs <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 292
Version: 1
Status: Developing
=head1 AB
> "NW" == Nathan Wiger <[EMAIL PROTECTED]> writes:
>> It sounds really stoopid to say C<$SIG{__WARN__}> on a machine which
>> doesn't have signals.
NW> Indeed. It is also worth noting that people on -flow have been hashing
NW> out safe signals through a "use signal" pragma, which wou
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
C<$^C> should be true when compiling
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 305
Version: 1
Status: Developing
=he
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
User-definable POD handling
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 306
Version: 1
Status: Developing
=head1 ABSTRA
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
subroutine / generic entity documentation
=head1 VERSION
Maintainer: Michael Maraist <[EMAIL PROTECTED]>
Date: 25 Aug 2000
Last Modified: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 176
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Case ignoring eq and cmp operators
=head1 VERSION
Maintainer: Markus Peter <[EMAIL PROTECTED]>
Date: 24 Aug 2000
Mailing List: [EMAIL PROTECTED]
Number: 143
Version: 2
Status: Retired
=head1 AB
On Mon, 25 Sep 2000, Nathan Wiger wrote:
> > perl -e 'print -rwx $_'
> > Can't call method "rwx" on an undefined value at -e line 1.
>
> Yeah, but read the error - Perl's parsing that as:
>
> [nwiger@matrix:~]$ perl -MO=Deparse -e 'print -rwx $_';
> print -$_->rwx;
> -e syntax
On Sun, Sep 24, 2000 at 08:52:23PM -, Perl6 RFC Librarian wrote:
> The solution is simple: All barewords must die.
This RFC makes no mention of what happens to the following constructs:
use Foo;
require Foo;
%foo = (bar => "baz");
These are legitimate, non-ambiguous uses of bar
On Mon, Sep 25, 2000 at 02:49:29PM -0400, Uri Guttman wrote:
> and how do they nest or get localized? with use signal you can install a
> lexically scoped handler or a package level handler. with WARN it looks
> like a global handler to me.
They're special subs. They nest and get localized like s
> "SC" == Simon Cozens <[EMAIL PROTECTED]> writes:
SC> On Mon, Sep 25, 2000 at 02:49:29PM -0400, Uri Guttman wrote:
>> and how do they nest or get localized? with use signal you can install a
>> lexically scoped handler or a package level handler. with WARN it looks
>> like a global h
On Mon, Sep 25, 2000 at 03:10:47PM -0400, Uri Guttman wrote:
> in what order? like BEGIN and END?
Whatever, yes.
> what if you wanted a block scoped warn handler?
What about it? (Or did someone eat the "local" keyword already?)
> i think it would be better to have some explicit way of
> sett
> "SC" == Simon Cozens <[EMAIL PROTECTED]> writes:
SC> On Mon, Sep 25, 2000 at 03:10:47PM -0400, Uri Guttman wrote:
>> in what order? like BEGIN and END?
SC> Whatever, yes.
>> what if you wanted a block scoped warn handler?
SC> What about it? (Or did someone eat the "local" key
> "Uri" == Uri Guttman <[EMAIL PROTECTED]> writes:
Uri> on the geek cruise, lincoln told me he had almost completed a total
Uri> rewrite of CGI.pm. i have not heard anything about it since then. we
Uri> should find out what he has done and possibly integrate it into perl6.
CGI 3.01 is in the
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
The AUTOLOAD subroutine should be able to decline a request
=head1 VERSION
Maintainer: Leon Brocard <[EMAIL PROTECTED]>
Date: 10 Aug 2000
Last Modified: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
On Mon, Sep 25, 2000 at 06:37:58PM -, Perl6 RFC Librarian wrote:
> This RFC proposes that the interface to Perl's source filtering facilities
> be made much easier to use.
Hm. I've just sent in the "line disciplines" RFC, which probably will end up
obsoleting a reasonable chunk of this.
--
Paul wrote:
> > Given this level of complexity, it's perhaps not surprising that source
> > code filtering is not commonly used.
>
> Whilst I don't have any problems with you module, I think you are
> overstating the complexity of the existing situation. This should be all
> t
On Mon, Sep 25, 2000 at 02:17:38PM -0700, Nathan Wiger wrote:
>import Foo;
You're beginning to blur your own fine line here. import is a class method
call using indirect object syntax.
> But notice the disconnect here:
>
>package Foo;
>use base 'Bar';
>
> Seems almost that:
>
>
> Perl currently only has C and C operators which work case-sensitively.
> It would be a useful addition to add case-insensitive equivalents.
As I recall, the consensus the last time this came up was that C and
C would be perfect examples w/in a RFC proposing a way to declare
a function to take
Michael Fowler wrote:
>
> You're beginning to blur your own fine line here. import is a class method
> call using indirect object syntax.
And, actually, per Schwern's RFC 253, require() would be too. Sometimes.
> stat->{'mode'}
>
> No ambiguity here.
So I assume you're suggesting that th
On Mon, 25 Sep 2000 10:22:46 -0400, Clayton Scott wrote:
>It:
> + stacks multiple tests quite cleanly without excess verbiage
> (if (-e && -T && -s && -x){...} gets a little tedious especially
> if you don't use $_)
Perhaps you want is to use $_. A "with" statement, or is it an
expression, s
Michael Fowler wrote:
>
> This RFC makes no mention of what happens to the following constructs:
>
> use Foo;
> require Foo;
I don't mind a very few special cases. I would imagine that these might
have to remain special:
use Foo;
require Foo;
import Foo;
package Foo;
But n
On Mon, Sep 25, 2000 at 03:50:20PM -0700, Nathan Wiger wrote:
> So I assume you're suggesting that this:
>
> stat->{'mode'}
>
> be a call to stat(), which returns a hashref, but this:
>
> stat->mode
>
> would be a call to the method mode() in the class 'stat'
>
> That's not how I read
> This is not a theoretical concern. If someone, at some point, defines sub
> CGI {} your constructor suddenly fails. If you're using something along the
> lines of Animal::Bear->new(), and the author of Animal.pm defines a Bear()
> method, your constructor suddenly fails. This is action at a d
On Mon, Sep 25, 2000 at 07:34:04PM -, Perl6 RFC Librarian wrote:
> Mailing List: [EMAIL PROTECTED]
Most of this RFC would probably be better off in perl6-stdlib; the debugger
isn't really part of the language. That being said, however...
> The ability to easily retrieve and edit your N mos
> This and other RFCs are available on the web at
> http://dev.perl.org/rfc/
>
> =head1 TITLE
>
> Provide a standard module to simplify the creation of source filters
>
> =head1 VERSION
>
> Maintainer: Damian Conway <[EMAIL PROTECTED]>
> Date: 20 September 2000
> Mailing List: [EMAIL PROTE
"John L. Allen" wrote:
>
> Ok, so that's pathological, but this isn't
>
> perl -e 'print -rwx($_)'
> Undefined subroutine &main::rwx called at -e line 1.
Well, it is still a little weird. You're still negating a subroutine
call. And remember, if you have a sub called "r" this do
This begs a question - How would this be implemented, knowing that at least
some MAJOR modules have what I call "run-time" dependencies, which are very
easy to do with Perl?
For example, what would this option think of DBI, for example, with it
loading DBD's based on subroutine parameters?
Or, s
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Compilation: Remove requirement for final true value in require-d and do-ed files
=head1 VERSION
Maintainer: Damian Conway <[EMAIL PROTECTED]>
Date: 7 Aug 2000
Last Modified: 25 Sep 2000
Mailing Lis
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Higher order functions
=head1 VERSION
Maintainer: Damian Conway <[EMAIL PROTECTED]>
Date: 4 Aug 2000
Last Modified: 25 Sep 2000
Number: 23
Version: 6
Mailing List: [EMAIL PROTECTED]
Status: Fr
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Objects : Core support for method delegation
=head1 VERSION
Maintainer: Damian Conway <[EMAIL PROTECTED]>
Date: 4 Sep 2000
Last Modified: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 193
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Subroutines: Extend subroutine contexts to include name parameters and lazy arguments
=head1 VERSION
Maintainer: Damian Conway <[EMAIL PROTECTED]>
Date: 17 Aug 2000
Last Modified: 25 Sep 2000
Mailin
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Objects : Private keys and methods
=head1 VERSION
Maintainer: Damian Conway <[EMAIL PROTECTED]>
Date: 1 Sep 2000
Last Modified: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 188
Version: 3
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Objects: C pragma
=head1 VERSION
Maintainer: Damian Conway <[EMAIL PROTECTED]>
Date: 14 Sep 2000
Last Modified: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 223
Version: 2
Status: Froze
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Fix iteration of nested hashes
=head1 VERSION
Maintainer: Damian Conway <[EMAIL PROTECTED]>
Date: 18 Sep 2000
Last Modified: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 255
Version: 3
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Objects : Native support for multimethods
=head1 VERSION
Maintainer: Damian Conway <[EMAIL PROTECTED]>
Date: 18 September 2000
Last Modified: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 25
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Builtins : Make use of hashref context for garrulous builtins
=head1 VERSION
Maintainer: Damian Conway <[EMAIL PROTECTED]>
Date: 19 Sep 2000
Last Updated: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Subroutines : Pre- and post- handlers for subroutines
=head1 VERSION
Maintainer: Damian Conway <[EMAIL PROTECTED]>
Date: 21 Sep 2000
Last Modified: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Numb
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Provide a standard module to simplify the creation of source filters
=head1 VERSION
Maintainer: Damian Conway <[EMAIL PROTECTED]>
Date: 20 Sep 2000
Last Modified: 25 Sep 2000
Mailing List: [EMAIL PR
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Function-call named parameters (with compiler optimizations)
=head1 VERSION
Maintainer: Michael Maraist <[EMAIL PROTECTED]>
Date: 25 Aug 2000
Last Modified: 25 Sep 2000
Mailing List: [EMAIL PROTECTE
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Detecting Perl Core Modules Should Be Easy
=head1 VERSION
Maintainer: Leon Brocard <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 291
Version: 1
Status: Developing
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
MT-Safe Autovariables in perl 5.005 Threading
=head1 VERSION
Maintainer: Michael Maraist <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 293
Version: 1
Status: Deve
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Internally, data is stored as UTF8
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 294
Version: 1
Status: Developing
=head1
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Normalisation and C
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 295
Version: 1
Status: Developing
=head1 ABSTRACT
Perl
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Getting Data Into Unicode Is Not Our Problem
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 296
Version: 1
Status: Developi
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Attributes for compiler hints
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 297
Version: 1
Status: Developing
=head1 ABST
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Make subroutines' prototypes accessible from Perl
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 298
Version: 1
Status: Dev
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
C<@STACK> - a modifyable C
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 299
Version: 1
Status: Developing
=head1 ABSTRAC
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Cache byte-compiled programs and modules
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 301
Version: 1
Status: Developing
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Unrolling loops and tail recursion
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 302
Version: 1
Status: Developing
=head1
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Keep C, but make it work.
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 303
Version: 1
Status: Developing
=head1 ABSTRACT
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
C algorithm to be selectable at compile time
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 304
Version: 1
Status: Developi
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Ban Perl hooks into regexes
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 308
Version: 1
Status: Developing
=head1 ABSTR
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Allow keywords in sub prototypes
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 309
Version: 1
Status: Developing
=head1 A
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Ordered bytecode
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 310
Version: 1
Status: Developing
=head1 ABSTRACT
Bytecod
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Line Disciplines
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 311
Version: 1
Status: Developing
=head1 ABSTRACT
B is wh
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Unicode Combinatorix
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 312
Version: 1
Status: Developing
=head1 ABSTRACT
How
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Perl 6 should support I18N and L10N
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 313
Version: 1
Status: Developing
=head
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
A parser is a many-layered thing
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 314
Version: 1
Status: Developing
=head1 A
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Kick out all ops - libprt
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 315
Version: 1
Status: Developing
=head1 ABSTRACT
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
C and C
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 300
Version: 1
Status: Developing
=head1 ABSTRACT
Perl 5.6's C is
At 09:34 AM 9/25/00 +0100, Simon Cozens wrote:
>Dan,
> I've finally woken up and I now have 8 RFCs on Unicode handling[1] I'm
>about to throw at the librarian. While I'm perfectly happy to have them
>disgust (sic.) here, I think it might be sensible to start up a WG for
>discussing Unicode Thi
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Implicit counter in for statements, possibly $#.
=head1 VERSION
Maintainer: John McNamara <[EMAIL PROTECTED]>
Date: 16 Aug 2000
Last Modified: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 1
> Add a new special variable, C<@STACK> to replace the C
> function. Allow people to modify the call stack in certain, very
> restricted ways.
> Perl 6 => Perl 5
> $STACK[-1] = [caller(0)];
> $STACK[-2] = [caller(1)];
I strongly agree with the opinion that we should try and get
> Ban Perl hooks into regexes
>
> =head1 ABSTRACT
>
> Remove C, C and friends.
>
At first, I thought you were crazy, then I read
>It would be preferable to keep the regular expression engine as
>self-contained as possible, if nothing else to enable it to be used
>either outside Perl or inside st
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Regex modifier for support of chunk processing and prefix matching
=head1 VERSION
Maintainer: Bart Lateur <[EMAIL PROTECTED]>
Date: 23 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 316
Version:
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Access to optimisation information for regular expressions
=head1 VERSION
Maintainer: Hugo van der Sanden ([EMAIL PROTECTED])
Date: 25 September 2000
Mailing List: [EMAIL PROTECTED]
Number: 317
Ve
Wouldn't this interact rather badly with the /gc option (which also leaves
C set on failure)?
This question arose because I was trying to work out how one would write a
lexer with the new /z option, and it made my head ache ;-)
> As you can see from the example code, the program flow stays
> I agree with both of you. It would be nice if @$ precedence worked as Bart
> specified, but I still think that arrays should be arrays.
The problem is that
$name = "myarray";
@$name = (1,2,3);
print @$name[0,1]; # 1,2
Is very consistent currently. Change one and you have to change t
On Mon, Sep 25, 2000 at 02:56:20AM -0500, Curtis Jewell wrote:
> Or would this tool be restricted to compile-time dependencies only?
I see no problem restricting dependency graphs to compile-time
dependencies.
Z.
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Replace localtime() and gmtime() with date() and utcdate()
=head1 VERSION
Maintainer: Nathan Wiger <[EMAIL PROTECTED]>
Date: 5 Aug 2000
Last Modified: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Simple assignment lvalue subs should be on by default
=head1 VERSION
Maintainer: Nathan Wiger <[EMAIL PROTECTED]>
Date: 24 Aug 2000
Last-Modified: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Numbe
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Transparently integrate C
=head1 VERSION
Maintainer: Nathan Wiger <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 319
Version: 1
Status: Developing
=head1 ABSTRACT
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Apache-like Event and Dispatch Handlers
=head1 VERSION
Maintainer: Nathan Wiger <[EMAIL PROTECTED]>
Date: 14 Aug 2000
Last Modified: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 101
Versi
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Common Callback API for all AIO calls.
=head1 VERSION
Maintainer: Uri Guttman <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 321
Version: 1
Status: Developing
=he
Dan,
I've finally woken up and I now have 8 RFCs on Unicode handling[1] I'm
about to throw at the librarian. While I'm perfectly happy to have them
disgust (sic.) here, I think it might be sensible to start up a WG for
discussing Unicode Things. I'm even fool enough to volunteer to chair it i
Nathan Wiger <[EMAIL PROTECTED]> writes:
> > >package Doggie;
> > >
> > >sub isborn {
> > >bless { @_ }, self; # ;-)
> > >}
> > >sub scratches ($\@;@) {
> > >...
> > >}
> > >
> > >
> > >package Doggie::Cute;
> > >
> > >use base 'Doggie';
> > >use
On Mon, Sep 25, 2000 at 06:02:51AM -, Perl6 RFC Librarian wrote:
> =head1 ABSTRACT
>
> 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
Adam Turoff wrote:
> I plan to offer a more formal RFC of this idea.
>
> =item perl6storm #0004
> Need perl to spit out pod/non-pod, like cc -E. Pod is too hard to parse.
> This would make catpod trivially implemented as a compiler filter.
Note that this functionality is trivial if RFC79 is imp
Nathan Wiger wrote:
> In fact, I'd much rather still a more generic function like 'want' that
> takes a list of things to check:
>
>file($file, 'd'); # is it a directory?
>file($file, 'wd'); # is it a writable directory?
if ( all { $_->($file) } \&writable, \&directory ) { ...
On Mon, Sep 25, 2000 at 01:55:10PM +0100, Richard Proctor wrote:
> It does not seem to have much to do with tr///, if you want it, why not put it
> in a module with some meaningful name such as histogram()?
Hm. Counting doesn't have much to do with tr///, if you think of it like that.
Now, if y
On Mon, 25 Sep 2000 14:44:16 +0100, Simon Cozens wrote:
>Incidentally, so what if a hash is slow? You pay for what you get. It's still
>quicker than doing it by hand.
This is for the cases where epeople forget that they are "asking" for
it. I don't want comp.lang.perl.misc or any other support c
On 25 Sep 2000 06:07:01 -0700, Randal L. Schwartz wrote:
>Bart> Plus, in Perl 5, NO core function returns a hash.
>Bart> None at all.
>
>It's not returning a hash. I like the proposal that has it return a
>paired list, similar to the semi-paired list we get with a capturing
>split, or a list-con
> =head1 TITLE
>
> First-Class CGI Support
> Perl6 should be *easier* to write CGI programs than Perl5. One way to
> accomplish this is to add a C<-cgi> option to Perl, so that all of the
> mechanical setup is done automatically. That setup could also be done
> through a C pragma.
>
> To ma
On 25 Sep 2000, Perl6 RFC Librarian wrote:
> =head1 TITLE
>
> Remove -X
>
> The prefered mechanism for file tests should be more legible, using
> terms like 'readable(FOO)' and 'writeable(FOO)' instead of the
> =head1 MIGRATION ISSUES
> Perl programmers happy with the -X syntax will need to
> Many mechanisms exist to make perl code and data persistant. They should
> be cleaned up, unified, and documented widely within the core
> documentation.
>
But doesn't this go against TMTOWTDI. :)
Different people might have different requirements. Portability would want
all ASCII, large app
On Mon, Sep 25, 2000 at 03:30:47PM +0200, Bart Lateur wrote:
> If you can garantee that it's also not using a hash internally to keep
> count, but instead a table parallel to the table that's being used to
> hold the conversion values, you've won me over.
Naturally, it's hard to guarantee anythin
Simon,
> I think I said in the RFC, didn't I? It's extending the counting use of tr///
> to allow you to count several different letters at once. For instance, letter
> frequencies in text is an important metric for linguists, codebreakers and
> others; think about how you'd get letter frequenc
1 - 100 of 190 matches
Mail list logo
