This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Simplifying split()
=head1 VERSION
Maintainer: Sean M. Burke <[EMAIL PROTECTED]>
Date: 30 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 361
Version: 1
Status: Developing
=head1 ABSTRACT
Per
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Allow multiply matched groups in regexes to return a listref of all matches
=head1 VERSION
Maintainer: Kevin Walker <[EMAIL PROTECTED]>
Date: 30 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 360
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Implementation of Threads in Perl
=head1 VERSION
Maintainer: Bryan C. Warnock <[EMAIL PROTECTED]>
Date: 1 Aug 2000
Last Modified: 28 September 2000
Mailing List: [EMAIL PROTECTED]
Number: 1
Vers
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Improvement needed in error messages (both internal errors and die function).
=head1 VERSION
Maintainer: S. A. Janet <[EMAIL PROTECTED]>
Date: 30 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 359
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Improvement needed in error messages (both internal errors and die function).
=head1 VERSION
Maintainer: S. A. Janet <[EMAIL PROTECTED]>
Date: 30 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 1
On Thu, 28 Sep 2000, David L. Nicol wrote:
> First we create a virtual environment to load the package into, then we
> define the methods we wish to overload, then we define all the methods
> to pass through the args -- No, this is not needed at all, we can use ISA
> for that can't we!
>
>p
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Remove long-deprecated $* (aka $MULTILINE_MATCHING)
=head1 VERSION
Maintainer: Hugo van der Sanden <[EMAIL PROTECTED]>
Date: 29 Sep 2000
Last Modified: 30 Sep 2000
Mailing List: [EMAIL PROTECTED]
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
New Perl Mascot
=head1 VERSION
Maintainer: David Grove <[EMAIL PROTECTED]>
Date: 28 Sep 2000
Last Modified: 30 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 343
Version: 2
Status: Frozen
=
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Consolidate the $1 and C<\1> notations
=head1 VERSION
Maintainer: David Storrs <[EMAIL PROTECTED]>
Date: 28 Sep 2000
Last Modified: 30 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 331
Versio
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Extend AUTOLOAD functionality to AUTOGLOB
=head1 VERSION
Maintainer: David Cantrell <[EMAIL PROTECTED]>
Date: 26 Sep 2000
Last Modified: 30 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 324
V
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 Sep 2000
Last Modified: 30 Sep 2000
Mailing List: [EMAIL PROTEC
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
Last Modified: 30 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 276
Version
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Arrays: Efficient Array Loops
=head1 VERSION
Maintainer: Buddha Buck <[EMAIL PROTECTED]>
Date: 8 Sep 2000
Last Modified: 30 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 207
Version: 3
Stat
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Extend regex syntax to provide for return of a hash of matched subpatterns
=head1 VERSION
Maintainer: Kevin Walker <[EMAIL PROTECTED]>
Date: 23 Aug 2000
Last Modified: 30 Sep 2000
Mailing List: [EMA
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Efficient numerics with perl
=head1 VERSION
Maintainer: pdl-porters team <[EMAIL PROTECTED]>
Date: 16 Aug 2000
Last Modified: 30 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 116
Version: 3
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Overloadable parentheses for objects
=head1 VERSION
Maintainer: pdl-porters team <[EMAIL PROTECTED]>
Date: 16 Aug 2000
Last Modified: 30 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 115
Vers
=head1 TITLE
Allow multiply matched groups in regexes to return a listref of all matches
=head1 VERSION
Maintainer: Kevin Walker <[EMAIL PROTECTED]>
Date: 30 Sep 2000
Version: 1
Mailing List: [EMAIL PROTECTED]
Status: Frozen
=head1 DESCRIPTION
Since the October 1 RFC deadline
=head1 TITLE
Extend regex syntax to provide for return of a hash of matched subpatterns
=head1 VERSION
Maintainer: Kevin Walker <[EMAIL PROTECTED]>
Date: 23 Aug 2000
Mailing List: [EMAIL PROTECTED]
Number: 150
Version: 2
Status: Frozen
=head1 ABSTRACT
Currently regexes retur
:The original proposal suggested that it would be nice if C in list
:context were to return the offset into the the target string where
:the match begins, as well as where it ends. Some people seemed to like
:this idea, so I am leaving it in, even though it no longer has much to
:do with the cont
On Fri, Sep 29, 2000 at 07:24:38PM -0400, Dan Sugalski wrote:
> > $foo = """Things like ', ", and \ have no special meaning in here.""";
>
> Argh! *NO*! That way lies madness, or at least DCL's quoting mania. My
> record, in a command procedure that wrote other command procedures that
> submi
On Sat, 30 Sep 2000, Bart Lateur wrote:
> I wrote this before, but apparently you didn't hear it. Let me repeat:
You're right, I missed your email when I was incorporating things
into the new version. Apologies.
> $foo on the LHS allows metacharacter matching, for example "a.*b" can
Bart Lateur <[EMAIL PROTECTED]> writes:
> But anyway: whould this imply that URL- and simple HTML escaping and
> back, will now be available through pack()/unpack()? Just like UUE?
> ;-)
Adding base64 encoding/decoding and quoted-printable would also be useful.
Either that, or taking uuenc
On 27 Sep 2000 07:36:42 -, Perl6 RFC Librarian wrote:
>Perl6 make it *easier* to write CGI programs than Perl5.
That is a strange sentence.
But anyway: whould this imply that URL- and simple HTML escaping and
back, will now be available through pack()/unpack()? Just like UUE?
;-)
-
I should have said: file-scoped lexical.
On Sat, 30 Sep 2000 21:56:43 +0100, Nicholas Clark wrote:
>If it's lexically scoped, would it be for arrays declared in that scope, or
>for arrays accessed in that scope?
>I'm not sure. I think I see potential breakage both ways.
You don't declare Perl a
Karl Glazebrook wrote:
> Ilya Zakharevich wrote:
> > On Thu, Sep 28, 2000 at 11:39:51AM -0400, Karl Glazebrook wrote:
> > > > > so what is wrong with the statement '@y = 3*@x;' then ?
> > > >
> > > > That other constructs *also* create an array context, in which the
> > > > behaviour of multiplica
Bart Lateur wrote:
> On 30 Sep 2000 20:13:55 -, Perl6 RFC Librarian wrote:
>
> >But setting $[ = 1 is the mathematically correct method for
> >array addressing and makes it easier for ordinary mortals to do
> >basic tasks with C, array addressing and the like.
>
> I sure don't want the fact t
On Saturday, September 30, 2000 3:13 PM, Perl6 RFC Librarian
[SMTP:[EMAIL PROTECTED]] wrote:
> This and other RFCs are available on the web at
> http://dev.perl.org/rfc/
>
> =head1 TITLE
>
> A Trademark on Perl Should be Acquired in Larry Wall's Name
>
Agreed. This is one of the few ways to pr
On 28 Sep 2000 19:40:01 -, Perl6 RFC Librarian wrote:
>=head2 How iterators might work in perl 6
>
>In perl 6 the keys and values functions should no longer use the
>same iterator as the each function - each use of keys and values
>should use it's own private iterator instead.
Is that per Da
On Sat, 30 Sep 2000 16:39:04 -0400, Adam Turoff wrote:
>I repeat:
>
>> >All of the other features offered by Lincoln Stein's CGI.pm should remain,
>> >but should not be deeply integrated into Perl6.
> ^^^
>:-)
>
>The proposed 'use cgi;' pragma is concerned with gluing Perl into a cgi
On Sat, Sep 30, 2000 at 09:56:43PM +0100, Nicholas Clark wrote:
> Similarly modules' formatting breaks if you set $/;
$\;
D'oh
> How many of the punctuation variables would be better with less-than-global
> scope?
Nicholas Clark
On Sat, Sep 30, 2000 at 10:34:40PM +0200, Bart Lateur wrote:
> On 30 Sep 2000 20:13:55 -, Perl6 RFC Librarian wrote:
>
> >But setting $[ = 1 is the mathematically correct method for
> >array addressing and makes it easier for ordinary mortals to do
> >basic tasks with C, array addressing and
On 28 Sep 2000 20:57:39 -, Perl6 RFC Librarian wrote:
>Currently, C<\1> and $1 have only slightly different meanings within a
>regex. Let's consolidate them together, eliminate the differences, and
>settle on $1 as the standard.
I wrote this before, but apparently you didn't hear it. Let me
On 30 Sep 2000 19:50:27 -, Perl6 RFC Librarian wrote:
>In Perl6, lookbehind in regular expressions should be extended to permit
>not only fixed-length, but also variable-length lookbehind.
I see no mention of negative lookbehind.
As I wrote before, in:
/(?
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
A Trademark on Perl Should be Acquired in Larry Wall's Name
=head1 VERSION
Maintainer: Bradley M. Kuhn <[EMAIL PROTECTED]>
Date: 30 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 354
Version: 1
On Wed, 27 Sep 2000 16:56:37 -0400, Dan Sugalski wrote:
>My gut feel is that there'll be a "default encoding" for filehandles and we
>*won't* try and get clever.
My gut feeling says that the text read from file should be treated as
native text, and should remain native text. I want plain Mac te
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
A Sandboxing mechanism for Perl 6
=head1 VERSION
Maintainer: Matthew Byng-Maddick <[EMAIL PROTECTED]>
Date: 30 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 353
Version: 1
Status: Developing
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Consolidate the $1 and C<\1> notations
=head1 VERSION
Maintainer: David Storrs <[EMAIL PROTECTED]>
Date: 28 Sep 2000
Last Modified: 30 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 331
Versio
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Global dynamic variables should remain the default
=head1 VERSION
Maintainer: Nathan Wiger <[EMAIL PROTECTED]>
Date: 28 Sep 2000
Last Modified: 30 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number:
On Sat, Sep 30, 2000 at 11:52:40AM -0500, David Grove wrote:
> That's the current running hope, I'll change the RFC to match it shortly.
> However, since I can't realistically expect this to happen, it wouldn't make
> sense to do more than suggest it as a first course of action.
I don't think i
On Tue, 26 Sep 2000 08:10:39 -0700, Nathan Wiger wrote:
>Well, you can easily do this already with
>
> $date = utcdate (time + $offset);
>
>Or even:
>
> $date = utcdate (time + &getoffset('US/Pacific'));
Unfortunately, because Daylight Saving Time is largely equivalent to
Time Zones, $offset
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
Last Modified: 30 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 319
Version: 2
Status
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Internal representation of Pseudo-hashes using attributes.
=head1 VERSION
Maintainer: Michael Maraist <[EMAIL PROTECTED]>
Date: 27 Sep 2000
Last Modified: 30 Sep 2000
Mailing List: [EMAIL PROTECTED]
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: 30 Sep 2000
Mailing List: [EMAIL PROTECTE
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Variable-length lookbehind.
=head1 VERSION
Maintainer: Peter Heslin <[EMAIL PROTECTED]>
Date: 9 Aug 2000
Last Modified: 30 Sept 2000
Mailing List: [EMAIL PROTECTED]
Number: 72
Version: 4
Stat
Hello David,
only one question:
i like the camel-icon very much.
maybe it is possible to convince O'Reilly, to donate
the trademark of the Camel, to larry?
regards
Gerrit
--
Gerrit Peter Haase
On Tue, 26 Sep 2000 11:55:32 +1100 (EST), Damian Conway wrote:
>Wouldn't this interact rather badly with the /gc option (which also leaves
>C set on failure)?
Yes.
The easy way out is disallow combining /gc wit h/z. But, since this
typically one of the applications it is aimed for, I should fin
That's the current running hope, I'll change the RFC to match it shortly.
However, since I can't realistically expect this to happen, it wouldn't make
sense to do more than suggest it as a first course of action.
On Saturday, September 30, 2000 6:48 AM, Gerrit Haase
[SMTP:[EMAIL PROTECTED]] wr
Alan Gutierrez wrote:
>
> This just in from RFC 2068 HTTP/1.1 - 4.2 Message Headers:
>
> The field value may be preceded by any amount of LWS, though a single SP
> is preferred. Header fields can be extended over multiple lines by
> preceding each extra line with at least one SP or HT.
Yes, sim
- Original Message -
From: "Bart Lateur" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Saturday, September 30, 2000 5:41 PM
Subject: Re: regexp RFCs: freeze 'em or lose 'em
> On Sat, 30 Sep 2000 13:55:40 +0100, Hugo wrote:
>
> >The RFCs listed below are still
On Sat, 30 Sep 2000 13:55:40 +0100, Hugo wrote:
>The RFCs listed below are still listed as 'developing'. The deadline is
>given as 1st October, but I'm not sure where the precise cutoff point
>is - Nat, can you confirm?
>
>As I understand it, RFCs not frozen by the deadline will be treated as
>wi
get rid of them all!!
Ilya Zakharevich wrote:
>
> On Thu, Sep 28, 2000 at 11:39:51AM -0400, Karl Glazebrook wrote:
> > > > so what is wrong with the statement '@y = 3*@x;' then ?
> > >
> > > That other constructs *also* create an array context, in which the
> > > behaviour of multiplication you
On Sat, 30 Sep 2000 00:57:47 +0100, Hugo wrote:
>:"local" inside embedded code will no longer be supported, nor will
>:consitional regexes. The Perl5 -> Perl6 translator should warn if it
>:ever encounters one of these.
>
>I'm not convinced that removing either of these are necessary to the
>main
The RFCs listed below are still listed as 'developing'. The deadline is
given as 1st October, but I'm not sure where the precise cutoff point
is - Nat, can you confirm?
As I understand it, RFCs not frozen by the deadline will be treated as
withdrawn. So please hurry.
If you make any substantial
Simon Cozens <[EMAIL PROTECTED]> writes:
> On Fri, Sep 29, 2000 at 04:13:46PM +0100, Piers Cawley wrote:
> > Did anyone suggest the following yet?
> > package Foo;
> > my sub _helper_function { ... }
>
> Todo:
> lexically scoped functions: my sub foo { ... }
> the basic conce
In <[EMAIL PROTECTED]>, Bart Lateur writes:
:Yes, but RFC 93 has some other disadvantages.
In respect of the number of calls, there seems nothing in RFC 93
to stop us permitting the callback to return more or fewer than the
requested number of characters. So a filehandle, for example, could
choos
On Fri, Sep 29, 2000 at 05:29:26PM -0700, David Olbersen wrote:
> -> -Original Message-
> -> From: Russ Allbery [mailto:[EMAIL PROTECTED]]
> -> Just out of curiosity, and I'm not objecting to this RFC, has anyone
> -> reading this mailing list actually intentionally used a vertical tab for
Nicholas Clark wrote:
>
> What do you mean by "need"? Strings need to be able to contain single
> quotes, but single quotes are not the only way to build a string. Single
> and double quotes don't generate a different fundamental type; a double
> quoted string with no variable interpolation also
On Thu, 28 Sep 2000 10:16:43 +0100, Tom Christiansen wrote:
>Try thinking of it this way: it's only a bareword if
>it would make use strict whinge at you.
So every bareword would be recognized as a sub. That, is nice. For
starters, Perl parsers can more easily recognize a sub name, without a
ne
On Sat, 30 Sep 2000 00:23:13 +0100, Hugo wrote:
>This is a strength of RFC 93 however, since in that context we
>don't need to restart the match each time we go off to fetch more
>data. In that situation if we run out of data after the 1234E2+2
>we fail the attempt to widen the \d+, match forward
[Grabbing an old thread...]
Ben Tilly wrote:
> My understanding is that the intent of the AL is to keep there from
> being a proprietary derivative named perl with restricted source. (If it
> is not named perl then that is explicitly allowed.)
I believe my draft of the Artistic License does
60 matches
Mail list logo
