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
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
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
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
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]
Something that I am a little stuck on...here is my understanding of the
way Perl is currently distributed and what it all means. I think I must
be confused about something...could someone straighten me out?
1) Works developed in Perl may be distributed under either the GPL or the
AL, dealer's ch
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.
On Mon, 25 Sep 2000, Ben Tilly wrote:
> Dan Sugalski wrote:
> >
> [...] I'm seriously thinking of instituting an "All
> >code
> >submitted to the repository belongs to Larry" rule until we have this
> >hashed out, so there's only one copyright holder to deal with.
>
> We had that discussion. Yo
> 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
Someone's been busy...
On Mon, 25 Sep 2000, Simon Cozens wrote:
> Data which comes in through a line discipline B be in UTF8, unless
> C is in force.
{snip}
> C just throws everything. None of the above happens.
What does "just throws everything" mean?
In RFC 294, data is internally stored in
The issue was closed ages ago. Continuing it in this direction is pointless.
However, I find it fascinating how tempting it seems to be for a moron to take
a cheap shot at someone trying to _correct_ a problem just because they've had
a few too many. Assuming that you have a remote clue, and ar
From: "Simon Cozens" <[EMAIL PROTECTED]>
> > A lot of what is trying to happen in (?{..}) and friends is parsing.
>
> That's not the problem that I'm trying to solve. The problem I'm trying
> to solve is interdependence. Parsing is neither here nor there.
Well, I recognize that your focus was no
From: "Hugo" <[EMAIL PROTECTED]>
> :Remove C, C and friends.
>
> Whoops, I missed this bit - what 'friends' do you mean?
Going by the topic, I would assume it involves (?(cond) true-exp |
false-exp).
There's also the $^R or what-ever it was that is the result of (?{ }).
Basically the code-like
I got seriously sidetracked the last two days, and did not get to my
hacks of license Ben wrote. However, I think that it probably needs a full
rewrite. I am going to try to write a clearer text license that tries to
do what Bens seems to want, and post it tommorrow. I like the idea that
Ben propo
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
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
PRAYER - what gets said when you C something
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Last Modified: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 307
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Handling environment setting in extension modules
=head1 VERSION
Maintainer: Jonathan Leffler <[EMAIL PROTECTED]>
Date: 25 September 2000
Mailing List: [EMAIL PROTECTED]
Number: 318
Version: 1
S
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
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
my Dog $spot should call a constructor implicitly
=head1 VERSION
Maintainer: Michael Fowler <[EMAIL PROTECTED]>
Date: 29 August 2000
Mailing List: [EMAIL PROTECTED]
Number: 171
Version: 3
Status
Buddha Buck wrote:
> The main problem I see are these:
>
> @array = ([1,2],[3,4]); # 2-dimensional array, using LOL syntax
> print $array[[1,1]]; # prints 4, OK
> print $array[1]; # prints ?
> print $array[[1,1,1]]; # prints ?
> print $array[[1]]; # prints ?
>
> Ac
> That is, the expression:
>
> $check = ^_ == ^_**2 *^_ or die ^_;
Shouldn't that be
$check = (^_ == ^_**2 *^_ or die ^_);
due to precedence of = over "or"?
> is equivalent to:
>
> $check = sub (;) {
> $_[0] == $_[1]**2 *$_[2] or die $_[3]
> };
> 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
Chris Nandor <[EMAIL PROTECTED]> writes:
> At 11:28 -0500 2000.09.25, David Grove wrote:
>> Evidently you've recognized a problem area that I may not have seen
>> before
> But you HAVE seen it before. You've specifically discussed this
> apparent problem on many occassions. Please do not be di
On Mon, Sep 25, 2000 at 10:08:38PM +0100, Simon Cozens wrote:
> On Mon, Sep 25, 2000 at 02:01:10PM -0700, Ask Bjoern Hansen wrote:
> > WORKING GROUP: perl6-internals-unicode
> > CHAIR: Simon Cozens <[EMAIL PROTECTED]>
> > DEADLINE:
>
> 16th October, extended if required
Please ignore me. I am a
On Mon, Sep 25, 2000 at 02:01:10PM -0700, Ask Bjoern Hansen wrote:
> WORKING GROUP: perl6-internals-unicode
> CHAIR: Simon Cozens <[EMAIL PROTECTED]>
> DEADLINE:
16th October, extended if required
> MISSION:
World dom.. oh, uhm.
Discuss RFCs 294, 295, 296, 300, 312, 313 and related RFCs. Repor
On Tue, Sep 26, 2000 at 01:19:16AM +0200, Bart Lateur wrote:
> Eh? Are you saying that Perl's error message should be adapted to the
> language of the computer user? I don't like that.
That's precisely what I am saying, yes, but I'm not wedded to the idea as a
religious principle. I think it woul
Bart Lateur <[EMAIL PROTECTED]> writes:
> Eh? Are you saying that Perl's error message should be adapted to the
> language of the computer user?
Yes. Most major free software packages already do this.
> I don't like that.
You can always not set the environment variables.
> How would Perl dec
> On Mon, Sep 25, 2000 at 08:56:47PM +, Mark-Jason Dominus wrote:
> > I think the proposal that Joe McMahon and I are finishing up now will
> > make these obsolete anyway.
>
> Good! The less I have to maintain the better...
Sorry, I meant that it would make (??...) and (?{...}) obsolete, no
Michael Maraist <[EMAIL PROTECTED]> writes:
> I suggested this a while ago, and the response was that automatically
> writing files is a security risk. You should extend your RFC to
> describe a caching directory or configuration.
This will be completely impossible to implement in some installa
On Mon, Sep 25, 2000 at 04:55:18PM -0400, Michael Maraist wrote:
> A lot of what is trying to happen in (?{..}) and friends is parsing.
That's not the problem that I'm trying to solve. The problem I'm trying
to solve is interdependence. Parsing is neither here nor there.
--
Intel engineering s
On Mon, Sep 25, 2000 at 08:56:47PM +, Mark-Jason Dominus wrote:
> I think the proposal that Joe McMahon and I are finishing up now will
> make these obsolete anyway.
Good! The less I have to maintain the better...
--
Keep the number of passes in a compiler to a minimum.
-- D
On Mon, Sep 25, 2000 at 11:31:08PM +0100, Hugo wrote:
> In <[EMAIL PROTECTED]>, Perl6 RFC Librarian writes:
> :=head1 ABSTRACT
> :
> :Remove C, C and friends.
>
> Whoops, I missed this bit - what 'friends' do you mean?
Whatever even more bizarre extensions people will have suggested by now...
-
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
> Instead of a whole new array, why not just add an additional variable to
> caller() that pops off that many stacks permanently?
>
>$pkg = caller(1); # back one stack frame
>$pkg = caller(1, 2);# back one stack, "pop" off
># two stack frames also
>
On 25 Sep 2000 20:15:19 -, Perl6 RFC Librarian wrote:
>Erreur de syntaxe. Syntaxfehler. Errore di sintassi. suntaktik'o sphalm'a.
>
>Perl 6 needs some kind of internationalisation and therefore message
>catalogue support. Really needs, with great urgency.
Eh? Are you saying that Perl's error
Bennett Todd wrote:
>
> If the only grounds is lack of interest, please just freeze it. It
> can be tossed later if people turn up strong counterarguments, like
> difficulting keeping the language's semantics intact or difficulty
> delivering better performance than perl5.
I agree. I haven't hea
> C should be renamed to C for Perl 6, and
Heh. I'm working on an integrated tie proposal right now that uses this
exact notion - and even a C naming scheme! I guess I'll be
referencing your RFC... ;-)
-Nate
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
> On Fri, 22 Sep 2000 08:58:10 +1100, Jeremy Howard wrote:
>
> >Bart Lateur wrote:
> >> Hmm... the problem is, I think, that array references and ordinary
> >> scalars are both scalars.
> >>
> >That's true, but they're scalars with different interfaces. In particular,
> >an array ref can be deref
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, Sep 25, 2000 at 05:35:09PM -0400, Michael Maraist wrote:
> In general, however, I don't see bytecode reading as being the real
> bottle-neck.
Quoting Nick Ing-Simmons in
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2000-05/msg01122.html:
"I have had similar doubts for some
In <[EMAIL PROTECTED]>, Perl6 RFC Librarian writes:
:Provide multiple sort algorithms, and have a pragma select which Perl
:uses; when a program is being compiled, analyze the data and
:heuristically select the better algorithm if possible.
Analysing at compile time seems real difficult. It would
> 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
Ilya Zakharevich wrote:
>
> On Sat, Sep 23, 2000 at 11:32:58AM -0400, Karl Glazebrook wrote:
> > Yes this is the point. I guess another way of looking at it is
> > saying that 3*@a operates in a list context not a scalar context
>
> Well, this shows that you entirely miss the problem of cryptoco
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:
>
>
In <[EMAIL PROTECTED]>, Perl6 RFC Librarian writes:
:=head1 ABSTRACT
:
:Remove C, C and friends.
Whoops, I missed this bit - what 'friends' do you mean?
Hugo
Simon Cozens <[EMAIL PROTECTED]> formally RFC'd:
> I have no idea how to implement tail recursion elimination, and I'd
> dearly love to learn. Unrolling loops with constant indices shouldn't be
> too hard.
AIUI you trigger your destructors on the appearance
of the "return" keyword rather than
Dan Sugalski wrote:
>
[...] I'm seriously thinking of instituting an "All
>code
>submitted to the repository belongs to Larry" rule until we have this
>hashed out, so there's only one copyright holder to deal with.
We had that discussion. You would be asking for copyright
assignment, which would
In <[EMAIL PROTECTED]>, Perl6 RFC Librarian writes:
: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 standalone translated Perl programs
:without a Perl runtime.
:
:To do this, we'll
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
"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 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
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
On Fri, 22 Sep 2000 08:58:10 +1100, Jeremy Howard wrote:
>Bart Lateur wrote:
>> Hmm... the problem is, I think, that array references and ordinary
>> scalars are both scalars.
>>
>That's true, but they're scalars with different interfaces. In particular,
>an array ref can be dereferenced and prov
At 03:57 PM 9/25/00 -0400, Ben Tilly wrote:
>Dan Sugalski wrote:
>[...]
>>>As soon as you get many implementations, you start to get into
>>>the portability nightmare. We differ on how much of a problem
>>>we think that is.
>>
>>Multiple implementations are good. All the languages that've had lon
> Ordered bytecode
>
> Bytecode should be structured in such a way that reading and executing
> it can be parallelised.
>
Are you suggesting a threaded VM? I know that the core is being rewritten,
so it's a possibility. If this is the case, then you'll want to reference
some of the other RFC's
At 02:01 PM 9/25/00 -0700, Ask Bjoern Hansen wrote:
>On Mon, 25 Sep 2000, Dan Sugalski wrote:
> > Ask, can you set up perl6-internals-unicode please?
>
>Sure. Fill in the blanks:
>
>WORKING GROUP: perl6-internals-unicode
>CHAIR: Simon Cozens <[EMAIL PROTECTED]>
>DEADLINE:
Oct 28, 2000
>MISSION:
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
> So, we check for the existence of a C<.plc> file before running a
> program; if the C<.plc> file is newer than the program, we use that
> instead. If there isn't a C<.plc> file or it's older than the program,
> recompile and dump the bytecode to a C<.plc> file. Naturally, this gives
> us the bes
Date: Sat, 23 Sep 2000 00:02:36 -0400
From: Wordsmith <[EMAIL PROTECTED]>
Subject: A.Word.A.Day--hyperbaton
To: [EMAIL PROTECTED]
hyperbaton (hye-PUR-buh-ton), noun, plural hyperbatons, hyperbata
The use, especially for emphasis, of a word order other than the
expected or usual one, as in
On Mon, 25 Sep 2000, Dan Sugalski wrote:
> 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 s
I think the proposal that Joe McMahon and I are finishing up now will
make these obsolete anyway.
> 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
> 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
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
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
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 RFC proposes a special sub, C, which is automatically called
> on Cing.
Damian already covered this issue very thoroughly in RFC 189:
"Hierarchical calls to initializers and destructors".
-Nate
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
RFC 189 covers this.
Damian
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
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
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
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
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
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
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
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
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
PRAYER - what gets said when you C something
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 307
Version: 1
Status: Developi
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
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
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
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
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
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
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
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
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
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
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
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
Dan Sugalski wrote:
[...]
>>As soon as you get many implementations, you start to get into
>>the portability nightmare. We differ on how much of a problem
>>we think that is.
>
>Multiple implementations are good. All the languages that've had long-term
>viability have had multiple implementations
At 01:22 PM 9/25/00 -0400, Ben Tilly wrote:
>Dan Sugalski wrote:
>>The more ubiquitous Perl the language (as opposed to perl the
>>implementation) is, the better off we all are. I, for one, would be
>>*thrilled* if once we got a solid reference doc out for perl 6 someone else
>>besides us wrote an
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
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
C is just an assertion
=head1 VERSION
Maintainer: Piers Cawley <[EMAIL PROTECTED]>
Date: 13 Sep 2000
Last Modified: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 218
Version: 2
Status: F
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
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
Interface polymorphism considered lovely
=head1 VERSION
Maintainer: Piers Cawley <[EMAIL PROTECTED]>
Date: 20 Sep 2000
Last Modified: 25 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 265
Vers
1 - 100 of 190 matches
Mail list logo
