On Thursday, September 28, 2000 10:33 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
>
> New Perl Mascot
>
> =head1 VERSION
>
> Maintainer: David Grove <[EMAIL PROTECTED]>
> Date: 28 Sep 2
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Putting an Event Loop in the Core
=head1 VERSION
Maintainer: Uri Guttman <[EMAIL PROTECTED]>
Date: 29 Sept 2000
Mailing List: [EMAIL PROTECTED]
Number: 345
Version: 1
Status: Developing
=head1
In 2 and a bit days all RFCs must be frozen--those not frozen will be
auto-retracted by the librarian! So, could you please freeze your RFCs--the
following have some still outstanding:
Ilya Zakharevich <[EMAIL PROTECTED]> 8
David Nicol <[EMAIL PROTECTED]> 2
Buddha Buck <[EMAIL PROTECTED]> 1
pdl-p
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Use features of portable, free compilers and libraries
=head1 VERSION
Maintainer: John Tobey <[EMAIL PROTECTED]>
Date: 5 Aug 2000
Last Modified: 28 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number:
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
Mailing List: [EMAIL PROTECTED]
Number: 343
Version: 1
Status: Developing
=head1 ABSTRACT
Perl has
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
unified container theory
=head1 VERSION
Maintainer: David Nicol <[EMAIL PROTECTED]>
Date: 28 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 341
Version: 1
Status: Developing
=head1 ABSTRACT
On Fri, Sep 29, 2000 at 02:15:25PM +1100, iain truskett wrote:
> * Daniel Chetlin ([EMAIL PROTECTED]) [29 Sep 2000 14:10]:
> > My RFC is predicated on the notion that perl5 will look enough like
> > perl6 that we won't have to rewrite all of the docs, and thus
> > there's plenty to be done as of n
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Thread Programming Model
=head1 VERSION
Maintainer: Steven McDougall <[EMAIL PROTECTED]>
Date: 31 Aug 2000
Last Modified: 28 Sep 2000
Version: 4
Mailing List: [EMAIL PROTECTED]
Number: 185
Sta
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Object neutral error handling via exceptions
=head1 VERSION
Maintainer: Glenn Linderman <[EMAIL PROTECTED]>
Date: 16 Aug 2000
Last Modified: 28 Sep 200
Mailing List: [EMAIL PROTECTED]
Number: 119
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Module Scope Control
=head1 VERSION
Maintainer: Bryan C. Warnock <[EMAIL PROTECTED]>
Date: 5 Aug 2000
Last Modified: 28 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 40
Version: 2
Status: F
* Daniel Chetlin ([EMAIL PROTECTED]) [29 Sep 2000 14:10]:
[...]
> My RFC is predicated on the notion that perl5 will look enough like
> perl6 that we won't have to rewrite all of the docs, and thus there's
> plenty to be done as of now. With all of these people flurrying about
> in excitement abo
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
On Thu, Sep 28, 2000 at 11:04:47PM -0400, Adam Turoff wrote:
> On Thu, Sep 28, 2000 at 07:56:49PM -0700, Daniel Chetlin wrote:
> > On Fri, Sep 29, 2000 at 12:56:44AM +0100, Simon Cozens wrote:
> > > Why isn't there a documentation w/g? Yes, this is a hint.
> >
> > My RFC 240 garnered exactly 0 re
At 07:56 PM 9/28/00 -0700, Daniel Chetlin wrote:
>On Fri, Sep 29, 2000 at 12:56:44AM +0100, Simon Cozens wrote:
> > Why isn't there a documentation w/g? Yes, this is a hint.
>
>My RFC 240 garnered exactly 0 responses, so there doesn't seem to be
>much of an interest. I was trying to decide today w
On Thu, Sep 28, 2000 at 07:56:49PM -0700, Daniel Chetlin wrote:
> On Fri, Sep 29, 2000 at 12:56:44AM +0100, Simon Cozens wrote:
> > Why isn't there a documentation w/g? Yes, this is a hint.
>
> My RFC 240 garnered exactly 0 responses, so there doesn't seem to be
> much of an interest. I was tryin
On Fri, Sep 29, 2000 at 12:56:44AM +0100, Simon Cozens wrote:
> Why isn't there a documentation w/g? Yes, this is a hint.
My RFC 240 garnered exactly 0 responses, so there doesn't seem to be
much of an interest. I was trying to decide today whether I should
freeze or withdraw.
-dlc
Alan Gutierrez wrote:
>
> This header functionality is application specific and does not belong in
> the core any more than the socket stuff which seems to be on its way
> out. I don't see why this has be implemented in the core in C.
>
> Once again, if core means core modules, and as a part of
I tried to contribute on this list but it seems we've coalesced downto Tom
and a handful of others. No one else has a voice.
I have nothing but respect for Tom, Nathan, et al, but its no longer my idea
of a community - more like a faction. I'm getting more into PHP now and
less into Perl, onl
> =item *
> C<\1> goes away as a special form
>
> =item *
> $1 means what C<\1> currently means (first match in this regex)
>
> =item *
> ${1} is the same as $1 (first match in this regex)
>
> =item *
> ${P1} means what $1 currently means (first match in last regex)
Here's the big problem with
> Is $$ the only alternative, or did I miss more? I don't think I've even
> seen this $$ mentioned before?
$$ is not a suitable alternative. It already means the current process
ID. It really cannot be messed with. And ${$} is identical to $$ by
definition.
> >I still like the idea of $$, as I d
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
with takes a context
=head1 VERSION
Maintainer: David Nicol <[EMAIL PROTECTED]>
Date: 28 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 340
Version: 1
Status: Developing
=head1 ABSTRACT
"cal
In <[EMAIL PROTECTED]>, Bart Lateur writes:
:I'll try to find that "thread" back.
This was my message:
http://www.mail-archive.com/perl6-language-regex%40perl.org/msg00354.html
:>I don't think changing /s is the right solution. I think this will
:>incline people to try and fix their problems
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
caller->eval BLOCK
=head1 VERSION
Maintainer: David Nicol <[EMAIL PROTECTED]>
Date: 28 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 339
Version: 1
Status: Developing
=head1 ABSTRACT
C is e
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
shareable bytecode
=head1 VERSION
Maintainer: Stéphane Payrard <[EMAIL PROTECTED]>
Date: 28 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 338
Version: 1
Status: Developing
=head1 ABSTR
On Thu, Sep 28, 2000 at 05:01:06PM -0700, Stephen Zander wrote:
> > "Stephen" == Stephen Zander <[EMAIL PROTECTED]> writes:
> Stephen> Not necessarily. Nat recently posted about his
> Stephen> misinterpretation of Larry's plans but said he still
> Stephen> planned to lean on peopl
In <[EMAIL PROTECTED]>, Perl6 RFC Librarian writes:
:The basic idea is to expand an array as a list of alternatives. There
:are two possible syntaxs (?@foo) and just plain @foo. @foo might just have
:existing uses (just), therefore I prefer the (?@foo) syntax.
That needn't be a problem, that's
Subject: ANNOUNCE: perl 6 released
From: John Macdonald <[EMAIL PROTECTED]>
Date: 1997/07/21
Message-Id: <[EMAIL PROTECTED]>
References: <5h3d45$mn3$[EMAIL PROTECTED]>
Organization: InterLog Internet Services
Reply-To: [EMAIL PROTECTED]
Newsgroups: comp.lang.perl.mod
In <[EMAIL PROTECTED]>, Perl6 RFC Librarian writes:
:=head1 TITLE
:
:Asignment within a regex
This document could do with running through a spellchecker.
:Potentially the $foo could be any scalar LHS, as in (?$foo{$bar}= ... )!,
:likewise the '=' could be any asignment operator.
It isn't clear
> "Stephen" == Stephen Zander <[EMAIL PROTECTED]> writes:
Stephen> Not necessarily. Nat recently posted about his
Stephen> misinterpretation of Larry's plans but said he still
Stephen> planned to lean on people to finish by October 1
Stephen> otherwise they'd never get done.
On Thu, Sep 28, 2000 at 04:54:36PM -0700, Stephen Zander wrote:
> Not necessarily. Nat recently posted about his misinterpretation of
> Larry's plans but said he still planned to lean on people to finish by
> October 1 otherwise they'd never get done.
Yuh, I just realised that the bulk of the on
> "Simon" == Simon Cozens <[EMAIL PROTECTED]> writes:
Simon> Hm. So this means there's no point me submitting anything
Simon> now, because it's not going to have time to be discussed
Simon> and frozen? G-r-reat.
Not necessarily. Nat recently posted about his misinterpretation of
On Thu, 28 Sep 2000 23:54:20 +0100, Hugo wrote:
>We thought of a few other possibilities too. I think it is a shame you
>did not mention them, and explain why your proposal is better.
Let me think on it.
Is $$ the only alternative, or did I miss more? I don't think I've even
seen this $$ mentio
In <[EMAIL PROTECTED]>, Perl6 RFC Librarian writes:
:MJD:
:Interpolated qr() items shouldn't be recompiled anyway. They should
:be treated as subroutine calls. Unfortunately, this requires a
:reentrant regex engine, which Perl doesn't have. But I think it's the
:right way to go, and it would so
Curtis Jewell <[EMAIL PROTECTED]> writes:
> Hmm... Isn't TAI->UTC RELATIVELY easy, but has accuracy loss? (I could
> be misinformed...) I'd just do two things, therefore:
TAI to UTC is easy and accurate if you have a current leap-seconds table.
(In fact, in order to get TAI, you probably convert
> >So anyhow, yes, this is a big, icky problem.
We want to subclass things but have them still retain their old pre-modification
names, w/o changing the thing we are altering (only masking it.)
Right?
Here's an alternate approach:
What if, instead of adding an additional and confusing bag of
In <[EMAIL PROTECTED]>, Perl6 RFC Librarian writes:
:In addition, pos() is set to the offset of the start of the recognized
:match prefix. In case of a plain succesful match, or of a normal
:not-found termination, pos is undef() on exit.
That's not entirely true - it depends on the flags. It is
- Original Message -
From: "Perl6 RFC Librarian" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, September 28, 2000 14:37
Subject: RFC 99 (v4) Standardize ALL Perl platforms on UNIX epoch
> The issue is still open as to whether or not time should be ma
On Thu, Sep 28, 2000 at 04:11:13PM -0700, Nathan Wiger wrote:
> Remember: Oct 1st is a true deadline, coming from the powers above,
> meaning if your RFC is not frozen by then, it will be auto-retracted
> and not considered.
Hm. So this means there's no point me submitting anything now, because
We've only got 4 days left until the One True Deadline on this whole
thing. Please, go check this out:
http://dev.perl.org/rfc/overdue-perl6-language-io.html
And get your RFC's finished up. Remember: Oct 1st is a true deadline,
coming from the powers above, meaning if your RFC is not frozen by t
We've only got 4 days left until the One True Deadline on this whole
thing. Please, go check this out:
http://dev.perl.org/rfc/overdue-perl6-language-objects.html
And get your RFC's finished up. Remember: Oct 1st is a true deadline,
coming from the powers above, meaning if your RFC is not frozen
In <[EMAIL PROTECTED]>, "Richard Proctor" writes:
:> I'd be more inclined to have callbacks registered for a word: that
:> way we can complain earlier when two modules try to register the
:> same word. Then at regexp-compile time we parse out the word
:> following the (+ and immediately know who t
In <[EMAIL PROTECTED]>, Perl6 RFC Librarian writes:
:Originally, we had thought of adding Yet Another Regex Modifier; but to
:be honest, having 2 modifiers just for the newline is already confusing
:enough, for too many people. A third is definitely out.
We thought of a few other possibilities to
Alan Gutierrez wrote:
>
> I still hope that it doesn't get as complicated as all this. I know
> there are arguments out there for specifying integer size and signedness
> but I can't imagine that adding this stuff is a good thing.
Key thing: This is all *optional*. This is *not* required. I cann
I don't like it, and here's why:
> currently single quoted here docs don't interpolate C<\\> or C<\'>.
We already have a way to read in arbitrary literals. I _like_ the
fact that C allows backslash to be used to allow including the delimiter.
It works for any delimiter, too, not just single-
:=item *
:/(foo)_$1_bar/
:
:=item *
:/(foo)_C<\1>_bar/
Please don't do this: write C or /(foo)_\1_bar/, but
don't insert C<> in the middle: that makes it much more difficult to
read.
:mean different things: the second will match 'foo_foo_bar', while the
:first will match 'foo[SOMETHING]bar' whe
> a design expressed in UML could be
> implemented in a non-OO language.
Interesting concept... "expressing" perl in UML would certainly add depth to the
artistic license ;)
> > I think, though, that the core interface should be procedural.
>
> I agree. We should not confuse OOD with OOP.
As
A few things I need to point out:
> use strict 'objects': a new pragma for using Java-like objects in Perl
RFC 278 had already supposedly claimed "use strict 'objects'", but this
is flexible.
> =head2 protected
>
> Just take Conway's RFC 188 and do a s/private/protected/g :-)
So you're sugges
On Wed, 27 Sep 2000 10:34:48 -0500, Jonathan Scott Duff wrote:
>If $1 could be made to work properly on the LHS of s///, I'd vote for
>that being The Way.
I disagree, because \1 is different from a variable $foo in at least two
ways:
* $foo is compiled into /$foo/ before anything is matched. \
On Thu, Sep 28, 2000 at 09:05:52PM -, Perl6 RFC Librarian wrote:
> =head1 TITLE
>
> use strict 'objects': a new pragma for using Java-like objects in Perl
> =head2 protected
>
> Just take Conway's RFC 188 and do a s/private/protected/g :-)
"protected" is a very loaded term. What you propo
On Thu, Sep 28, 2000 at 08:57:39PM -, Perl6 RFC Librarian wrote:
> ${P1} means what $1 currently means (first match in last regex)
I'm sorry that I don't have anything more constructive to say than
"ick", but ... Ick.
Well, maybe I do. Forget $P1. If the user wanted $1 from the
previous R
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
use strict 'objects': a new pragma for using Java-like objects in Perl
=head1 VERSION
Mantainer:Marco Marongiu <[EMAIL PROTECTED]>
Date: 28 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 336
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: 27 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 1
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Class Methods Introspection: what methods does this object support?
=head1 VERSION
Maintainer: Mark Summerfield <[EMAIL PROTECTED]>
Date: 28 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 335
Ve
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Perl should allow specially attributed subs to be called as C functions
=head1 VERSION
Maintainer: Dan Sugalski <[EMAIL PROTECTED]>
Date: 28 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 334
Ve
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Regex: Make /$/ equivalent to /\z/ under the '/s' modifier
=head1 VERSION
Maintainer: Bart Lateur <[EMAIL PROTECTED]>
Date: 28 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 332
Version: 1
Sta
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
Mailing List: [EMAIL PROTECTED]
Number: 331
Version: 1
Status: Developing
=
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
Mailing List: [EMAIL PROTECTED]
Number: 330
Version: 1
Stat
Simon Cozens wrote:
>
> On Thu, Sep 28, 2000 at 10:00:49AM -0400, Andy Dougherty wrote:
> > On Wed, 27 Sep 2000, Nathan Wiger wrote:
> > > Y'know, I couldn't have said this better myself. :-) I've always felt
> > > that "use English" was a waste of time and effort, a bandaid trying to
> > > act a
Dan Sugalski wrote:
> At 07:38 PM 9/28/00 +, Perl6 RFC Librarian wrote:
> >These APIs should be documented separately from the implementation, in a
> >language-independent and an object-oriented way.
>
> Unfortunately the two conflict. C, APL, Fortran, and COBOL aren't
> particularly object-
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
C
=head1 VERSION
Maintainer: Simon Cozens <[EMAIL PROTECTED]>
Date: 28 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 329
Version: 1
Status: Developing
=head1 ABSTRACT
A pragma to modify the
At 07:38 PM 9/28/00 +, Perl6 RFC Librarian wrote:
>These APIs should be documented separately from the implementation, in a
>language-independent and an object-oriented way.
Unfortunately the two conflict. C, APL, Fortran, and COBOL aren't
particularly object-oriented... Not that I disagree
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Single quotes don't interpolate \' and \\
=head1 VERSION
Maintainer: Nicholas Clark <[EMAIL PROTECTED]>
Date: 28 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 328
Version: 1
Status: Developin
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
C<\v> for Vertical Tab
=head1 VERSION
Maintainer: Nicholas Clark <[EMAIL PROTECTED]>
Date: 26 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 327
Version: 1
Status: Developing
=head1 ABSTRACT
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Method calls SHOULD suffer from ambiguity by default
=head1 VERSION
Maintainer: Nathan Wiger <[EMAIL PROTECTED]>
Date: 24 Sep 2000
Last Modified: 28 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number
Nathan Torkington writes:
> So that Larry isn't chasing a moving target, I've set a deadline of
> August 1 for freezing the RFCs. Ziggy has come up with a list of
As Tim pointed out and most people correctly surmised, I meant
October. YAPC::Europe must have addled my brain. The deadline is
Oct
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Implementation of hash iterators
=head1 VERSION
Maintainer: Tom Hughes <[EMAIL PROTECTED]>
Date: 20 Aug 2000
Last Modified: 28 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 136
Version: 3
S
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Components in the Perl Core Should Have Well-Defined APIs and Behavior
=head1 VERSION
Maintainer: Bradley M. Kuhn <[EMAIL PROTECTED]>
Date: 17 Aug 2000
Last Modified: 28 Sep 2000
Mailing List: [EMAI
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Standardize ALL Perl platforms on UNIX epoch
=head1 VERSION
Maintainer: Nathan Wiger <[EMAIL PROTECTED]>
Date: 14 Aug 2000
Last Modified: 28 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 99
V
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
The Copyright and Licensing Working Group
=head1 VERSION
Maintainer: Bradley M. Kuhn <[EMAIL PROTECTED]>
Date: 2 Aug 2000
Last MOdified: 28 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 13
Ve
On Thu, Sep 28, 2000 at 02:40:04PM -0400, John Porter wrote:
> Tom Christiansen wrote:
> > Perl's use of @ISA is beautiful.
> >
> > use base is, or can be, pretty silly --
> > think pseudohashes, just for one.
>
> I suppose you diddle @INC directly, Tom,
> instead of use'ing lib?
I call "non
On Thu, Sep 28, 2000 at 08:06:42AM +0200, H . Merijn Brand wrote:
> On 27 Sep 2000 07:36:42 -, Perl6 RFC Librarian <[EMAIL PROTECTED]> wrote:
> > This and other RFCs are available on the web at
> > http://dev.perl.org/rfc/
> >
> > =head1 TITLE
> >
> > First-Class CGI Support
>
> Freezing
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 propose is not appropriate.
>
> for example?
A prototypel
Andy Dougherty <[EMAIL PROTECTED]> writes:
> I find that I don't remember many of the less-frequently-used perlvars
> (where less-frequently-used depends on the types of programs I write,
> obviously). I certainly couldn't tell you off-hand the differences
> among $< $> $( and $). I'd have to l
Jonathan Scott Duff wrote:
>
> 1. Allow the first argument to split() to be a number such that
>the string is broken into chunks of that many characters.
@strings = /(.{$n})/g;
> 2. Allow the first argument to split() to be an array of
>numbers, such t
Tom Christiansen wrote:
>
> Perl's use of @ISA is beautiful.
>
> use base is, or can be, pretty silly --
> think pseudohashes, just for one.
I suppose you diddle @INC directly, Tom,
instead of use'ing lib?
--
John Porter
Nathan Wiger wrote:
> 1. make a listref only for multiple values:
>@name = @{$CGI{name}} if ( ref $CGI{name} eq 'ARRAY' );
Ick. That piece of code is small enough, but it's going to end up
replicating itself everywhere %CGI is accessed. This will be a fruitful
new source of bugs when people
On Thu, Sep 28, 2000 at 01:02:11PM -0500, Jonathan Scott Duff wrote:
> I thought I had sent this the other day, but it doesn't appear to have
> made it through...
>
> Here are a couple of ideas that I don't have time to RFC, but some who
> likes them might:
>
> 1. Allow the first argumen
I thought I had sent this the other day, but it doesn't appear to have
made it through...
Here are a couple of ideas that I don't have time to RFC, but some who
likes them might:
1. Allow the first argument to split() to be a number such that
the string is broken into chunks o
Buddha Buck wrote:
>
> While Perl -lets- every function be well prototyped, it doesn't -require-
> every function to be well prototyped. Because of this, it might be well
> nigh impossible to eliminate all ambiguity to the compiler.
Well, right. Clearly, in those cases, you can expect to nee
On Thu, 28 Sep 2000, Steve Fink wrote:
> Tom Christiansen wrote:
> >
> > As we sneak under the wire here, I'm hoping someone
> > has posted an RFC that alters the meaning of my/local.
> > It's very hard to explain as is. my is fine, but local
> > should be changed to something like "temporary" (
Tom Christiansen wrote:
>
> As we sneak under the wire here, I'm hoping someone
> has posted an RFC that alters the meaning of my/local.
> It's very hard to explain as is. my is fine, but local
> should be changed to something like "temporary" (yes, that
> is supposed to be annoying to type) or
Webmaster wrote:
>
> (I have attached a prototype of what I had in mind)
>
> From: "David L. Nicol" <[EMAIL PROTECTED]>
> > Yes, that is exactly what is being suggested, but the "indexof" function
> > is implicit in the attribute. Your code becomes
> >
> > print "Found It at position ${_:n}!\n"
At 03:48 PM 9/28/00 +, John van V wrote:
>How would the byte-compiled caches relate to the compiled C code XS'd into
>the modules??
When a module is built, in addition to transforming any XS code (or
whatever it ultimately is) into an executable, perl will also compile any
perl code into b
On Thu, Sep 28, 2000 at 10:00:49AM -0400, Andy Dougherty wrote:
> On Wed, 27 Sep 2000, Nathan Wiger wrote:
> > Y'know, I couldn't have said this better myself. :-) I've always felt
> > that "use English" was a waste of time and effort, a bandaid trying to
> > act as a tourniquet.
>
> I think it's
How would the byte-compiled caches relate to the compiled C code XS'd into the
modules??
Could it be embedded, I think not, but please enlighten me.
Ilya Zakharevich 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 propose is not appropriate.
for example?
> I did not see any viable proposal on changing things in a majo
> A future protocol could well require things in order. Hence you're
> having the output headers in order. Therefore you should have the input
> ones available in order as well.
I don't see a reason why an @HTTP ordered and %HTTP unordered couldn't
both be supported.
> I'm thinking a $headers_i
Tom Christiansen wrote:
>
> >So what's left?
> >
> >print STDERR "Foo";
> >
> >We have a proposal to turn STDERR into $STDERR, and it looks likely it'll go
> >through.
>
> It is? I certainly hope not. It makes as much sense to
> do that as to force a dollar sign on subroutines.
Your point
Piers Cawley wrote:
>
> > >I strongly agree with the opinion that we should try and get away from
> > >special variables and switches in favor of functions and pragmas.
> > >Witness 'use base' instead of '@ISA', 'use warnings', and so on.
> >
> > Huh? Why??? Perl's use of @ISA is beautiful. It
On Wed, 27 Sep 2000, Nathan Wiger wrote:
> Russ Allbery wrote:
> >
> > I've found the use of use English in code I had to maintain to be annoying
> > and unhelpful, and to actually degrade the maintainability of the code
> Y'know, I couldn't have said this better myself. :-) I've always felt
> t
Certainly numbers should never be "zero-padded"!
Visit our website at http://www.ubswarburg.com
This message contains confidential information and is intended only
for the individual named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please
You also didn't mention that you would have broken the symmetry between
my Dog $spot;
our Dog $spot;
Or that constructors have no (and should have no) set name in Perl.
--tom
Visit our website at http://www.ubswarburg.com
This message contains confidential information and is intended
Tom Christiansen <[EMAIL PROTECTED]> writes:
> >I strongly agree with the opinion that we should try and get away from
> >special variables and switches in favor of functions and pragmas.
> >Witness 'use base' instead of '@ISA', 'use warnings', and so on.
>
> Huh? Why??? Perl's use of @ISA is
* Philip Newton ([EMAIL PROTECTED]) [28 Sep 2000 21:19]:
> On 27 Sep 2000, at 23:48, iain truskett wrote:
> > So surely you'd want %HTTP (the input headers) to also be an array
> > rather than a hash, since they'd be required in order as well?
> I don't care, because I don't work with this much.
On 27 Sep 2000, at 23:48, iain truskett wrote:
> So surely you'd want %HTTP (the input headers) to also be an array
> rather than a hash, since they'd be required in order as well?
I don't care, because I don't work with this much. And I don't know
whether I'd need to bear in mind the protocol
To my mind, things would be a lot clearer if my and local were to change
places - but I can see why that would not be a good thing.
If it's not too late for suggestions for renaming local, what about
'override'.
Dave.
- Original Message -
From: "Michael Fowler" <[EMAIL PROTECTED]>
To: "T
On Wed, Sep 27, 2000 at 09:31:59PM -0400, Bennett Todd wrote:
> How so? Seems to run straightforward comparable stuff a bit quicker
> than perl; doesn't seem to take any more effort to express a good
> many things.
This is becoming off topic; I have an interview with Matz regarding his
thoughts a
On Thu, Sep 28, 2000 at 08:17:40AM +0200, H.Merijn Brand wrote:
> Can I forward this to perl.comp.lang.misc and perl.comp.lang.moderated?
Please feel free.
> Maybe it's more in brian's lane to spot these messages and react on them,
Well, yes, Perl 6 has been getting a bit of a bad press, and,
On Wed, Sep 27, 2000 at 10:09:40PM -0400, Bennett Todd wrote:
> I think we proponents of this RFC believe it may well make _some_
> things easier, with the implementation of perl6 being among them.
Could you explain how this would make the implementation of Perl 6 easier?
I *really* can't see tha
In <[EMAIL PROTECTED]>, Tom Christiansen writes:
:>I consider recursive regexps very useful:
:>
:> $a = qr{ (?> [^()]+ ) | \( (??{ $a }) \) };
:
:Yes, they're "useful", but darned tricky sometimes, and in
:ways other than simple regex-related stuff. For example,
:consider what happens if you
1 - 100 of 108 matches
Mail list logo
