On Wed, Aug 16, 2000 at 11:15:40PM -0700, Peter Scott wrote:
>
>Sorry I didn't chime in earlier, but I would like to say that I prefer
>published deadlines. Reason: people will talk for as long as you give
>'em. However long a meeting is scheduled for, that's how long it will
>take. We're al
At 04:12 PM 8/17/00 +1000, [EMAIL PROTECTED] wrote:
>On Wed, Aug 16, 2000 at 10:35:09AM -0700, Nathan Wiger wrote:
> >I agree. I think the trend should be to establish some permanent
> >sublists, which we're informally leaning towards already. Something
> >like:
> >
> > -io = ALL I/O issue
On Wed, Aug 16, 2000 at 10:35:09AM -0700, Nathan Wiger wrote:
>I agree. I think the trend should be to establish some permanent
>sublists, which we're informally leaning towards already. Something
>like:
>
> -io = ALL I/O issues, like open/socket/filehandles
> -subs = ALL sub/method/
On Tue, Aug 15, 2000 at 08:05:25PM -, Perl6 RFC Librarian wrote:
>=head1 TITLE
>
>lvalue subs should receive the rvalue as an argument
>
>=head1 VERSION
>
>Maintainer: Andy Wardley <[EMAIL PROTECTED]>
>Date: 15 Aug 2000
>Version: 1
>Mailing List: [EMAIL PROTECTED]
>Number:
On Wed, Aug 16, 2000 at 12:15:30PM -0500, David L. Nicol wrote:
>
>If "catch" can be defined DURING PARSING
>
>and SYNTAX ERRORS are catchable
>
>error handling can be used to define otherwise
>undefined syntax, becoming a macro language.
Please take this to the -errors sublist. Thanks...
K.
-
Jarkko Hietaniemi [mailto:[EMAIL PROTECTED]] wrote:
>
> On Wed, Aug 16, 2000 at 09:49:36AM -0400, Stephen P. Potter wrote:
> > Lightning flashed, thunder crashed and Jonathan Scott Duff
> <[EMAIL PROTECTED]> whispered:
> > | Um, it's not guaranteed to blow up in 2038. That's an
> implementatio
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Better constants and constant folding
=head1 VERSION
Maintainer: John Siracusa <[EMAIL PROTECTED]>
Date: Aug 15 2000
Last-Modified: Aug 16 2000
Version: 2
Mailing List: [EMAIL PROTECTE
Chaim Frenkel wrote:
> > "KH" == Kai Henningsen <[EMAIL PROTECTED]> writes:
>
> KH> Hashes and arrays, OTOH, really aren't different for people. The
concept
> KH> of an index needing to be a nonnegative number is a computer concept.
>
> I don't know about that. Good old PL/I had arbitrary rang
> "NW" == Nathan Wiger <[EMAIL PROTECTED]> writes:
NW> The concept isn't that hard ":lvalue makes it so you can assign to
NW> subs". But the hard part is deciding *where* it should be used. I think
NW> it puts an unfair burden on a CPAN author to try and forsee all the
NW> possible uses of a
> "JS" == John Siracusa <[EMAIL PROTECTED]> writes:
JS> On 8/16/00 12:37 PM, Perl6 RFC Librarian wrote:
>> It is proposed that a new syntax for declaring constants be introduced:
>>
>> my $PI : constant = 3.1415926;
>> my @FIB : constant = (1,1,2,3,5,8,13,21);
>> my %ENG_ERRORS : constant =
> "KH" == Kai Henningsen <[EMAIL PROTECTED]> writes:
KH> Hashes and arrays, OTOH, really aren't different for people. The concept
KH> of an index needing to be a nonnegative number is a computer concept.
I don't know about that. Good old PL/I had arbitrary ranges for array
indices.
Hmm, I
> "JSD" == Jonathan Scott Duff <[EMAIL PROTECTED]> writes:
JSD> On Wed, Aug 16, 2000 at 12:48:12PM -0400, Dan Sugalski wrote:
>> At 11:09 AM 8/16/00 -0400, John Porter wrote:
>> >The difference between numbers and strings is analogous to --
>> >or, on further reflection, IDENTICAL to -- the d
On Wed, 16 Aug 2000, Perl6 RFC Librarian wrote:
> This will ignore all leading white space on each line until the end terminator
> is found. It effectively does s/^\s*// before processing each following line.
I don't agree with this, but
> It also ignores whitespace (but not the line termi
Chaim Frenkel wrote:
>
> NW> P.S. If you're not on -io, this implicitly means you DON'T CARE and are
> NW> willing to accept whatever we come up with. So, everyone that's
> NW> interested please get on -io. Thanks again.
>
> That's a bit strong. All we are doing is filtering the garbage for Larr
> Either one or both of:
> Perl <-> Perl cross system will break.
> Perl <-> other program same system will break.
>
> Pick your poison. I'd rather have cross system break. But if the
> epoch were available then an adjustment could be made intellegently.
I'd take choice (b). I wa
On Wed, Aug 16, 2000 at 08:22:16PM -0400, Chaim Frenkel wrote:
> > "MF" == Michael Fowler <[EMAIL PROTECTED]> writes:
>
> MF> So what's insufficient about:
>
> MF> print <<"EOF";
> MF> Stuff
> MF> More stuff
> MF> Even more stuff
> MF> EOF
>
>
> Counting
> "MF" == Michael Fowler <[EMAIL PROTECTED]> writes:
MF> So what's insufficient about:
MF> print <<"EOF";
MF> Stuff
MF> More stuff
MF> Even more stuff
MF> EOF
Counting spaces, why make the programer work. Are those tabs or spaces?
And it doesn't strip t
> "NT" == Nathan Torkington <[EMAIL PROTECTED]> writes:
NT> Chaim Frenkel writes:
>> [use wacky Unicode characters for new operators]
>> I can see that this would give problems for current editors and displays,
>> but by the time perl6 comes out, perhaps the situation would be better.
NT> No
> "BB" == Buddha Buck <[EMAIL PROTECTED]> writes:
BB> stat() returns time stamps (made in the past). utime() sets time
BB> stamps. They should be compatible with time(). e.g., "utime
BB> time,time,@files" should still set the modify and access times of
BB> @files to "now".
With or without
On Wed, Aug 16, 2000 at 05:36:25PM -0400, Karl Glazebrook wrote:
> My take: I like perl, I don't mind it the way it is. But I'd be happier if
> it was a lot more like python! (indentation aside)
Why, then, don't you just use Python?
I'm not being sarcastic. Python is a very good language. It h
> "NW" == Nathan Wiger <[EMAIL PROTECTED]> writes:
NW> P.S. If you're not on -io, this implicitly means you DON'T CARE and are
NW> willing to accept whatever we come up with. So, everyone that's
NW> interested please get on -io. Thanks again.
That's a bit strong. All we are doing is filterin
> "TB" == Tim Bunce <[EMAIL PROTECTED]> writes:
TB> On Wed, Aug 16, 2000 at 05:23:04PM +1000, [EMAIL PROTECTED] wrote:
>> OK, weekly report. Ugh.
TB> Shouldn't these to go -announce as well?
I thought we agreed that they percolate upward.
The containing WG would report the results upward
On Wed, Aug 16, 2000 at 09:04:00PM +0200, Kai Henningsen wrote:
> And context dependency is bad for people.
Actually, people deal very well with context dependency.
"Have you paid Bill?"
"Have you paid that bill?"
"It looks like a duck's bill."
"The President vetoed the bill."
> A rose
On Wed, Aug 16, 2000 at 05:34:51PM -0400, Karl Glazebrook wrote:
> > You appear to arguing that expressions in function argument lists should
> > not be evaluated in a list context. Is this really what you mean?
>
> I guess I do. I guess I just hate contexts!
Context is a fundemental part of Pe
Today around 7:17pm, Casey R. Tweten hammered out this masterpiece:
: Today around 2:34pm, Nathan Wiger hammered out this masterpiece:
:
: : > Think on this:
: : >
: : > use perlrc qw/Resource1 Resource5/; # Import only named 'Resources'
: : >
: : > use perlrc qw/:all/;# Import
Today around 2:34pm, Nathan Wiger hammered out this masterpiece:
: > Think on this:
: >
: > use perlrc qw/Resource1 Resource5/; # Import only named 'Resources'
: >
: > use perlrc qw/:all/;# Import all 'Resources'
:
: > This sounds much more managable than a .perlrc that get's a
Real quick:
On Wed, 16 Aug 2000, John Porter wrote:
> grep() always treats its "second" arg as a list, even if it's a scalar,
> or some other list-of-one (or none); and grep() always returns a list,
> even if it's a list of one (or none).
True on the first part, false on the second. In scalar c
John Porter wrote:
> Mike Pastore wrote:
> Highlander variables acknowledge the fact that all variable types (scalar,
> array, hash) are simply objects. Objects of different classes, sure; but
> still just objects.
Not in Perl.
> You get no visual help in cases like
>
> $dog->bark();
On 8/16/00 4:00 PM, Perl6 RFC Librarian wrote:
> =head1 TITLE
>
> Better constants and constant folding
>
> =head1 VERSION
>
> Maintainer: John Siracusa <[EMAIL PROTECTED]>
> Date: Aug 15 2000
> Version: 1
> Mailing List: [EMAIL PROTECTED]
> Number: 113
This RFC has been integrated with RF
Mike Pastore wrote:
>
> Scenario 2:
>
> ret = grep(/hand/, var);
>
> *puzzled expression* "Grepping a scalar for a string? Grepping a list for
> a string? Returning a list or a scalar?"
You have failed to enter the mind of an expert perl programmer. ;-)
grep() always treats its "second"
> What makes Perl feel like Perl is, of course, subjective, but to me
> the punctuation is a lot of it. We're trying to improve Perl, not
> replace it.
This is an extremely loaded statement, and we've been hearing it a lot.
RFC 0, remember? Invoking RFC0 immediately after stating your own
per
On Wed, 16 Aug 2000, David Corbin wrote:
> Mike Pastore wrote:
>
> > $hashish{'dog'}# one whutzit
> > @hashish{'dog', 'cat'} # more than one whutzits
> > each %hashish # one whutzit, indexed
> > %hashish # all whutzits, indexed
> > keys %hashish
Karl Glazebrook wrote:
> Jon Ericson wrote:
> > I've spent almost a day trying to come up with a polite response to this
> > suggestion. I have started this mail 3 or 4 times but deleted what I
> > wrote because it was too sarcastic, angry or dismissive. This RFC
>
> Thanks!
>
> > strikes to t
- Original Message -
From: "Jonathan Scott Duff" <[EMAIL PROTECTED]>
Sent: Wednesday, August 16, 2000 10:00 AM
Subject: Re: Make lvalue subs the default (was Re: RFC 107 (v1) lvalue subs
should receive the rvalue as an argument)
> On Wed, Aug 16, 2000 at 12:14:09AM -0700, Nathan Wiger wr
Karl Glazebrook writes:
> Well said!
>
> My take: I like perl, I don't mind it the way it is. But I'd be happier if
> it was a lot more like python! (indentation aside)
This begs the question of why you're not using python. If it's just
indentation, that's silly. Surely there are patches to th
Stephen P. Potter wrote:
> Lightning flashed, thunder crashed and Perl6 RFC Librarian
<[EMAIL PROTECTED]>
> whispered:
> | =head1 TITLE
> |
> | Builtin: partition
> |
> | =head1 ABSTRACT
> |
> | It is proposed that a new function, C, be added to Perl.
> | C would return @list broken into
> | refe
Karl Glazebrook wrote:
> Nathan Wiger wrote:
> > Yeah, and isn't it cool that Perl gives you easy access to using and
> > understanding such complex data structures:
> >
> >print @{ $cars->{$model} };
> >
> > That "junk" makes it easy to see that you're derefencing a hashref that
> > contains
Nathan Torkington wrote:
> Perl6 RFC Librarian writes:
> > It is proposed that in a list context, operators are applied
> > component-wise to their arguments. Furthermore, it is proposed that
> > this behaviour be extended to functions that do not provide a specific
> > list context.
>
> I don't m
Well said!
Nathan Torkington wrote:
>
> Dan Sugalski writes:
> > Unfortunately, I think you're somewhat under-informed as to the inherent
> > capabilities of people's brains.
>
> Ok, at this point I think all parties have to step away and let the
> RFCs fall where they will.
>
> It's obvious
Nathan Torkington wrote:
> Piers Cawley writes:
> > > > The $a and $b of the sort comparator were A Bad Idea to begin with.
> > >
> > > Ditto. Can we ditch these in Perl 6? Don't see why $_[0] and $_[1]
can't
> > > be used, or even a more standard $1 and $2. Either one makes it more
> > > obvious
Jon Ericson wrote:
> I've spent almost a day trying to come up with a polite response to this
> suggestion. I have started this mail 3 or 4 times but deleted what I
> wrote because it was too sarcastic, angry or dismissive. This RFC
Thanks!
> strikes to the very heart of Perl as far as I'm c
Chaim Frenkel writes:
> CN> Can we please cut down on the traffic to perl-announce, maybe make it
> CN> moderated? Thanks,
>
> Perhaps, the esteemed Librarian could make the -announce a Bcc?
One of the moderators was a little too approval-happy. I believe
this has been fixed as of a few hours
Well said!
My take: I like perl, I don't mind it the way it is. But I'd be happier if
it was a lot more like python! (indentation aside)
I guess the question arises - how radical is perl6 allowed to be?
Karl
Kai Henningsen wrote:
> And context dependency is bad for people.
>
> There is a reas
Dan Sugalski writes:
> Unfortunately, I think you're somewhat under-informed as to the inherent
> capabilities of people's brains.
Ok, at this point I think all parties have to step away and let the
RFCs fall where they will.
It's obvious that there are two types of people: those who don't mind
Damien Neil wrote:
> What makes you presume this? Perhaps snrub() is something like this:
>
> sub snrub {
> foreach (@_) {
> frobnicate $_;
> }
> }
>
> You appear to arguing that expressions in function argument lists should
> not be evaluated in a list context. Is this real
> Think on this:
>
> use perlrc qw/Resource1 Resource5/; # Import only named 'Resources'
>
> use perlrc qw/:all/;# Import all 'Resources'
> This sounds much more managable than a .perlrc that get's applied globaly
> without asking for it.
Bingo. This feature should be off by de
On Wed, Aug 16, 2000 at 01:51:09PM -0600, Nathan Torkington wrote:
> Nathan Wiger writes:
> > Nonetheless, I think a better thing would be to figure out if it's
> > possible to "fix" this issue. I would *really* like lvalue subs ==
> > rvalue subs.
>
> I think conflating:
>foo(@vals)
> and
>
On Wed, Aug 16, 2000 at 08:03:31PM -, Perl6 RFC Librarian wrote:
> Perl should provide a mechanism to have common code autoloaded from a
> file. . . .
> A C file could be used to set system-wide defaults that
> the system administrator would like to promote. For instance,
> C could turn on
On Wed, Aug 16, 2000 at 02:38:33PM -0400, Uri Guttman wrote:
> i see problems with overlapping areas. I/O callbacks fall under both io
> and flow IMO. some of the error handling like dying deep in eval and
> $SIG{DIE} also fall under error and flow.
This is true, and inevitable. But IMHO it'd b
Kai Henningsen <[EMAIL PROTECTED]> writes:
> That would be nice if the punctuation actually *were* part of the
> variable name.
> However, it isn't: to access 'second', you'd say $args[1], NOT @args[1].
> It's one of the Perl features that most confuses newcomers.
Well, I think it is; it's just
Karl Glazebrook wrote:
>
> Jon Ericson wrote:
> > But @ and % provide important context clues (if not to perl than
> > certainly for programmers). We could also eliminate the plural case in
> > English, but this would be endlessly confusing for native speaker
> > (err... speakers). Why not chan
At 09:49 PM 8/16/00 +0200, Kai Henningsen wrote:
>[EMAIL PROTECTED] (Dan Sugalski) wrote on 15.08.00 in
><[EMAIL PROTECTED]>:
>
> > At 06:04 PM 8/15/00 -0400, John Porter wrote:
> > >Dan Sugalski wrote:
> > > > >Generality good.
> > > >
> > > > For many things, yes. For computers, say. For peopl
Today around 8:03pm, Perl6 RFC Librarian hammered out this masterpiece:
: This and other RFCs are available on the web at
: http://dev.perl.org/rfc/
:
: =head1 TITLE
:
: Perl resource configuration
:
: =head1 VERSION
:
: Maintainer: Jonthan Scott Duff <[EMAIL PROTECTED]>
: Date: 16 Aug
> "CN" == Chris Nandor <[EMAIL PROTECTED]> writes:
CN> Can we please cut down on the traffic to perl-announce, maybe make it
CN> moderated? Thanks,
Perhaps, the esteemed Librarian could make the -announce a Bcc?
--
Chaim FrenkelNonlinear Knowledge,
Perl6 RFC Librarian writes:
> It is proposed that in a list context, operators are applied
> component-wise to their arguments. Furthermore, it is proposed that
> this behaviour be extended to functions that do not provide a specific
> list context.
I don't mind making Perl's builtins do this. M
On Wed, Aug 16, 2000 at 03:05:23PM -, Perl6 RFC Librarian wrote:
> With a here doc print < the text of the here doc, is processed verbatum. This results in Here Docs
> that either stick out in the code, or result in unwanted leading whitespace.
> There are several FAQs that relate to this pro
> I think conflating:
>foo(@vals)
> and
>foo() = @vals
>
> is misleading and going to cause more confusion that it solves.
In simple cases, yes. The above looks misleading. Advanced stuff like
chaining though would be really cool. I could come up with oodles of
examples. :-)
> What kind
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Perl syntax support for ranges
=head1 VERSION
Maintainer: pdl-porters team <[EMAIL PROTECTED]>
Date: 16 August 2000
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: 117
=head1 ABSTRACT
This RF
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Default methods for objects
=head1 VERSION
Maintainer: pdl-porters team <[EMAIL PROTECTED]>
Date: 16 August 2000
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: 115
=head1 ABSTRACT
This RFC p
On Wed, Aug 16, 2000 at 01:07:24PM -0700, Peter Scott wrote:
> At 08:03 PM 8/16/00 +, Perl6 RFC Librarian wrote:
> >Perl should provide a mechanism to have common code autoloaded from a
> >file.
>
> Please, no. It's the ultimate scary action-at-a-distance.
If the programmer *wants* action-a
On 8/16/00 3:55 PM, John Siracusa wrote:
> On 8/16/00 12:37 PM, Perl6 RFC Librarian wrote:
>> This RFC proposes that the current constant.pm module removed, and
>> replaced with a syntax allowing any variable to be marked as constant.
>
> Unfortunately, I submitted an nearly identical RFC yesterd
On 16 Aug 2000, Kai Henningsen wrote:
> > This is very Perlish to me; the punctuation is part of the variable name
> > and disambiguates nicely. I'd be very upset if this idiom went away.
>
> That would be nice if the punctuation actually *were* part of the variable
> name.
>
> However, it i
At 08:03 PM 8/16/00 +, Perl6 RFC Librarian wrote:
>Perl should provide a mechanism to have common code autoloaded from a
>file.
Please, no. It's the ultimate scary action-at-a-distance.
I spent several years doing X programming. Ever seen the flowchart for how
resources are resolved? Let
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Perl resource configuration
=head1 VERSION
Maintainer: Jonthan Scott Duff <[EMAIL PROTECTED]>
Date: 16 Aug 2000
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: 114
=head1 ABSTRACT
Perl should
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Better constants and constant folding
=head1 VERSION
Maintainer: John Siracusa <[EMAIL PROTECTED]>
Date: Aug 15 2000
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: 113
=head1 AB
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Scope of Polymorphic References and Objects
=head1 VERSION
Maintainer: Syloke Soong <[EMAIL PROTECTED]>
Mailing List: [EMAIL PROTECTED]
Date: 15 Aug 2000
Last-Modified: 16 Aug 2000
Versi
On 8/16/00 12:37 PM, Perl6 RFC Librarian wrote:
> This RFC proposes that the current constant.pm module removed, and
> replaced with a syntax allowing any variable to be marked as constant.
Unfortunately, I submitted an nearly identical RFC yesterday because I
didn't see the existing one (I searc
s/PSEUDO\S?HASH/STRUCT/g
Nathan Wiger writes:
> Nonetheless, I think a better thing would be to figure out if it's
> possible to "fix" this issue. I would *really* like lvalue subs ==
> rvalue subs.
I think conflating:
foo(@vals)
and
foo() = @vals
is misleading and going to cause more confusion that it solves.
>
Glenn Linderman wrote:
>
> This deserves a "me too".
>
> Perl6 RFC Librarian wrote:
>
> > The camel and the docs include this example:
>
> >if (/Time: (..):(..):(..)/) {
> > $hours = $1;
> > $minutes = $2;
> > $seconds = $3;
> > }
> >
> > This then becomes:
> >
[EMAIL PROTECTED] (Dan Sugalski) wrote on 15.08.00 in
<[EMAIL PROTECTED]>:
> The ultimate target of a program's source code is the *programmer*.
True.
> Programmers, being people (well, more or less... :), work best with symbols
> and rich context.
This particular programmer *hates* what Per
[EMAIL PROTECTED] (Nathan Wiger) wrote on 15.08.00 in
<[EMAIL PROTECTED]>:
> > I'd say, if the variable exists, interpolate it. If not, print it as
> > it stands.
>
> I initially was thinking this too, but there's a major problem:
>
>print "Your stuff is: @stuff\n";
>
> I want this to *alw
[EMAIL PROTECTED] (Jonathan Scott Duff) wrote on 15.08.00 in
<[EMAIL PROTECTED]>:
> You're right, there should be just one date/time routine. But it is
> *extremely* difficult to incorporate time zones in a portable fashion.
> They change at legislative whim. But if utcdate() (or whatever we
[EMAIL PROTECTED] (Russ Allbery) wrote on 15.08.00 in
<[EMAIL PROTECTED]>:
> > All variables should be C<$x>. They should behave appropriately
> > according to their object types and methods.
>
> No thanks. I frequently use variables $foo, @foo, and %foo at the same
> time when they contain th
[EMAIL PROTECTED] (Nathan Torkington) wrote on 15.08.00 in
<[EMAIL PROTECTED]>:
> * you misunderstand the purpose of $ and @, which is to indicate
>singular vs plural.
Yes. That's one of the things that's wrong with it - maybe the biggest of
all.
It's one of the things that require con
[EMAIL PROTECTED] (Nathan Torkington) wrote on 15.08.00 in
<[EMAIL PROTECTED]>:
> Stephen P. Potter writes:
> > Why is it silly? Hashes and arrays are *conceptually* very similar
> > (even if they are extremely different implementation-wise).
>
> If that were the case, I think students would h
[EMAIL PROTECTED] (Dan Sugalski) wrote on 15.08.00 in
<[EMAIL PROTECTED]>:
> At 06:04 PM 8/15/00 -0400, John Porter wrote:
> >Dan Sugalski wrote:
> > > >Generality good.
> > >
> > > For many things, yes. For computers, say. For people, no. Generality
> > > bad. Specificity and specialization go
Nathan Torkington wrote:
>
> > Then I think both of these should act exactly the same:
> >
> > somesub(@values);
> > somesub = @values;
>
> EUGH. No way!
>
> Assignment should be used to reflect (get this) assignment. Using
> it as argument passing is disgusting. I'm assuming you're n
Nathan Torkington wrote:
>
> I think I failed to explain Damian's use of the word 'dangerous'.
>
> my $var;
> sub routine {
> $var;
> }
>
> This, by virtue of rvalue subs being default, keeps the lexical $var
> private. Damian's big on privacy.
> (2) Changing variables in the subrou
Jonathan Scott Duff wrote:
>
> Hrm. Perhaps you aren't explaining yourself clearly. Let's pretend
> that there is a magical value called $LVALUE that contains the thing
> being assigned. Are you saying that in
>
> somesub = $value;
>
> the subroutine C, being lvaluable by default is f
Nathan Wiger writes:
> sub somesub {
> my(@stuff) = @_;
> # do nothing
> }
>
> Then I think both of these should act exactly the same:
>
> somesub(@values);
> somesub = @values;
EUGH. No way!
Assignment should be used to reflect (get this) assignment. Using
it
The penguin module, as written about in an early TPJ
http://cpan.valueclick.com/authors/id/F/FS/FSG/
is a way to mask off part of the functionality of your perl
in order to "sandbox" with very fine grained control.
Let's put that into the core of perl6, the ability to
turn features off, part
Seems like the results of
@b = 1 .. 10;
for ( 1 .. 3 )
{ push @a, pop @b;
}
and
@b = 1 .. 10;
push (@a, pop ( @b, 3 ));
But this RFC makes it seem like they produce different results in @a. One could
argue that the current definition of unshift has a similar problem, and that you
are "preserv
> i see problems with overlapping areas. I/O callbacks fall under both io
> and flow IMO. some of the error handling like dying deep in eval and
> $SIG{DIE} also fall under error and flow.
True. But it should be up to the RFC author to choose the relevant list.
I think RFC authors have been prett
John Porter <[EMAIL PROTECTED]> writes:
> Russ Allbery wrote:
>> $args = 'first second third';
>> @args = split (' ', $args);
>> my $i = 0;
>> %args = map { $_ => ++$i } @args;
>> This is very Perlish to me; the punctuation is part of the variable
>> name and disambiguates nicely
On Wed, Aug 16, 2000 at 12:15:30PM -0500, David L. Nicol wrote:
> If "catch" can be defined DURING PARSING
>
> and SYNTAX ERRORS are catchable
>
>
> error handling can be used to define otherwise
> undefined syntax, becoming a macro language.
And AUTOLOAD can go away too! :-)
-Scott
--
Jona
> "NW" == Nathan Wiger <[EMAIL PROTECTED]> writes:
NW> I agree. I think the trend should be to establish some permanent
NW> sublists, which we're informally leaning towards already. Something
NW> like:
NW>-io = ALL I/O issues, like open/socket/filehandles
NW>-subs
Bart Lateur wrote:
>
> To me, a program is much like a maze, a
> multilevel walk in an old castle.
And if you commit a faux pas of some kind, the guards show
up and "throw" you off the north tower.
--
David Nicol 816.235.1187 [EMAIL PROTECTED]
At 11:17 PM 8/15/00 -0400, Chaim Frenkel wrote:
> > "NT" == Nathan Torkington <[EMAIL PROTECTED]> writes:
>
>NT> Chaim Frenkel writes:
> >> Why? What is the gain? Perl only runs on the local machine.
>
>NT> Epoch seconds are a convenient representation for dates and times.
>NT> Varying epochs
> "GB" == Graham Barr <[EMAIL PROTECTED]> writes:
GB> On Wed, Aug 16, 2000 at 10:49:16AM -0500, Jarkko Hietaniemi wrote:
>> On Wed, Aug 16, 2000 at 04:41:33PM +0100, Graham Barr wrote:
>> > On Wed, Aug 16, 2000 at 10:20:28AM -0500, Jonathan Scott Duff wrote:
>> > > > m//gt would be de
Stephen P Potter <[EMAIL PROTECTED]> writes:
> What stops us from imposing order on this chaos? If they are currently
> defined as not having any specific order, why can't we say they always
> return in numeric || alphabetic || ASCII || whatever order we want?
Because the fewer guarantees you m
The poll can't have been exhaustive.
I like these magic variables that depend on currently selected
fie handles, they remind me of Pascal's C construction
for entering the name space of a record structure.
Anyone for generalizing "select" to a more general "with" keyword
which would operate
Jarkko Hietaniemi writes:
> > Better would be to redefine what m//g means in a scalar context.
> >
> > $_ = "foofoofoofoofoofoofoo";
> > $count = m/foo/g;
> >
> > 1 is just as true as 7.
>
> I like this. No extra //modifiers to learn.
scalar context of /g is already defined to be som
> And I'm not proposing that this should change, just that import should
> be spelled "IMPORT". The perl5 to perl6 translator would simply do
> s/import/IMPORT/g (okay, not *simply*, but you get the drift)
So in your code, if you wanted to explicitly import something you'd have
to write:
req
Say we allow instantly tied lazy subroutine definitions
like so:
@naturals = (? { my $x=1; yield $x++ while 1 })
Is the code block in there a subroutine or a method?
And why?
How about using the eminently deprecatable "reset" operator
to start a tied lazy array back at it's "original"
"Bryan C. Warnock" wrote:
>
> ... is the cause for this. All the discussion is taking place in the
> master list before the sublists are spawned. You can only express the
> opinion that foo is not bar and never should be so many times.
I agree. I think the trend should be to establish some perm
Nathan Torkington wrote:
> John Porter writes:
> > foo $= ( bar, quux ); # provide scalar context to both sides
> > foo @= ( bar, quux ); # provide list context to both sides
>
> I assume you've dropped this idea as well, given the argument that you
> would be dropping prefix symbols bu
Peter Scott writes:
> >You're right. If RFC 45 is implemented they would however be inconsistent.
>
> No, || is half-consistent at the moment: the left hand side is forced into
> scalar context but the result context propagates down the right hand
> side. I challenge anyone to come up with a r
Jonathan Scott Duff wrote:
> As for $a[$something], if @a had been declared as
> "my @a : assoc;", then perl should stringify $something, otherwise
> numify. Hmm.. I guess this implies that all hashes need to be
> pre-declared. :-(
That was kinda along the lines of my suggestion; that the behav
At 10:53 AM 8/16/00 -0400, Stephen P. Potter wrote:
>Lightning flashed, thunder crashed and Perl6 RFC Librarian
><[EMAIL PROTECTED]>
> whispered:
>| =head1 TITLE
>|
>| Eliminate the optional C for C etc block declarations
>
>It seems to me it makes more sense to require the sub, but to move them
1 - 100 of 218 matches
Mail list logo
