> > Isn't this better handled with a (revamped and faster) tie?
> >
> > tie %professors, 'Tie::Sorted', ^a->name cmp ^b->name;
> >
> > tie %students, 'Tie::Sorted',
> >$$students{^1}{GPA} <=> $$students{^0}{GPA} };
> >
> > Damian
>
> It's a shorthand for i
On Thu, Aug 17, 2000 at 05:10:40PM -0400, Buddha Buck wrote:
> SO what you are saying is that the proper execution of "$p->foo(@args) +=
> $val;" should be (equivalent to):
>
> 1. Evaluate $val and get an rvalue $rval.
> 2. Evaluate $p->foo(@args) and get an lvalue $lfoo.
The order of those tw
On Fri, Aug 18, 2000 at 07:20:28AM +0100, Graham Barr wrote:
> So it is a security issue then as it needs somewhere to cache these
> object files, and anyone must be able to do it.
No more insecure than having your own LIB directory, although the prospect of
every user having their own copy of ev
On Fri, Aug 18, 2000 at 12:25:42AM -0400, Chaim Frenkel wrote:
> As Graham pointed out, is an lvalue sub supposed to act like a tie or
> like a variable.
Both.
As Damian points out the lvalue sub must return something that can
be used as an lvalue. Normal assignment hen happens.
So the result w
Perl6 RFC Librarian wrote:
> =head1 TITLE
>
> Default methods for objects
>
> =head1 ABSTRACT
>
> This RFC proposes syntactic support for default methods
> that can be defined for blessed references. This would
> allow the brackets C<()>, C<{}> and C<[]> to be used
> for a variety of convenien
On Thu, Aug 17, 2000 at 05:26:18PM -0400, Sam Tregar wrote:
> On Thu, 17 Aug 2000, Nick Ing-Simmons wrote:
> > Simon Cozens <[EMAIL PROTECTED]> writes:
> > >Wow. I'm sold. Can this be how we should be doing XS in Perl 6?
> > So we now run equivalent of xsubpp and cc every time script is run?
>
>
subscribe by sending mail to
[EMAIL PROTECTED]
more information at http://dev.perl.org/lists
LIST: perl6-language-data
CHAIR: Jeremy Howard <[EMAIL PROTECTED]>
MISSION:Discuss and draft RFCS for Perl 6 language features
related to the Perl Data Languag
Glenn Linderman wrote:
>
> Peter Scott wrote:
>
> > I have often wished that digraphs were not bundled with variables in this
> > respect, i.e., I wanted to put a string containing \n inside single quotes
> > just 'cuz it didn't contain variables to be interpolated. Whether there's
> > a way of
"David L. Nicol" wrote:
>
> What if its a method of anything in an array? $_ is already
> a reference to the object on the array in for loops rather
> than a copy of it. What if we make change be not something about
> for loops, but about anything in an array?
>
> print "The index, in
>>-io = ALL I/O issues, like open/socket/filehandles
>>-subs = ALL sub/method/func issues, like lvalue subs
>>-strict = ALL lexical/global variable scoping issues
>>-objects = ALL OO and module issues
>>-flow = ALL flow/threading issues
>>-errors = ALL er
On Thu, Aug 17, 2000 at 09:19:20AM -0700, Peter Scott wrote:
>
>I realize this is very pedestrian compared to the exception-handling stuff
>we've been tossing around, which could largely be said to render the issue
>moot; but I thought I'd shake the branches anyway and see what fell out.
>
>I'm
This discussion should be on the -datetime sublist. Please do not
discuss this RFC any further on the main language list.
K.
--
Kirrily Robert -- <[EMAIL PROTECTED]> -- http://netizen.com.au/
Open Source development, consulting and solutions
Level 10, 500 Collins St, Melbourne VIC 3000
Phone:
> Mmm... yummy... And placeholder names seem to be getting a real
> role in life too! I wonder if hashes used as HOF arguments in
> general should use placeholder names to fill in their arguments
> from the corresponding hash elements. That would be even yummier!
Personally I think an
Peter Scott wrote:
>
> I still think the explanation can be made simpler with fewer
> forward references. I'll have another try: [snip, but save]
>
> I note that under these rules it would be possible to have
> "try { ... } finally { }" with no catch blocks. I guess
> that's okay.
Have I got n
Damian Conway wrote:
> Suppose C were a built-in function with parameter list:
>
> sub with (\%; ^&) {...}
>
> That is, C takes an explicit hash and -- optionally -- a block, sub
ref,
> or higher order function.
> <...>
> If C is called with *both* a hash and a block/sub ref/h.o.f. as
> arguments,
I'm obviously missing something about vtables. It'll be obvious when someone
corrects me, but...
Currently, SvPVX(foo) requires one lookup; with a vtable, it would necessitate
two, (One to find the functino in "foo", and then the functino must find the
data in "foo") given that C, beastly as it i
Peter Scott wrote:
>
> Tony Olekshy wrote:
> >
> > trap { $@->{message} =~ /divide by 0/ } catch { ... }
>
> I don't think you need another keyword here. Just support an
> expression argument to catch and you can do
>
> catch $@->{message} =~ /divide by 0/ { ... }
>
> If it needs t
sub p{
print "Debug: @_\n";
@_;
};
Solved my problem :)
Nathan Wiger wrote:
>
> I think [a print() that returns the value of what you
> printed ] is an excellent idea independent of others and should
> probably be RFC'ed separately. Since it d
> DC> * Label an argument such that there is no corresponding named
> DC> parameter.
>
> Could this be eased slightly? How about a %rest hash, if supplied
> in the prototype would absorb the unused named parameters?
Yes, I've been rethinking that in light of my i
> On Thu, Aug 17, 2000 at 10:48:25PM -0500, David L. Nicol wrote:
> > Lets use hats again then.
> >
> > %ws{
> > print ^$height; #prints $ws{height}
> > print $height; # perl5 visibility rules
> > };
>
> But no $ for the keys of %ws.
>
>
> "DC" == Perl6 RFC Librarian <[EMAIL PROTECTED]> writes:
DC> * Label an argument such that there is no corresponding named
DC> parameter.
Could this be eased slightly? How about a %rest hash, if supplied
in the prototype would absorb the unused named parameters?
DC> =hea
Jonathan Scott Duff wrote:
> But no $ for the keys of %ws.
>
> %ws {
> print ^height; # prints $ws{height}
> print $height; # prints $height
> }
I'm thinking that ^name is short for $^name is short for ${^name}
and the longer version is what you
"J. David Blackstone" wrote:
>
> 1) Eliminate dynamic variables entirely.
Don't think there's a win. You'll need something identically like it,
which means you'll have to put lexicals in the symbol table, which means
they're just dynamics again...
Dynamic variables aren't evil, they're just misu
On Thu, Aug 17, 2000 at 10:48:25PM -0500, David L. Nicol wrote:
> Lets use hats again then.
>
> %ws{
> print ^$height; #prints $ws{height}
> print $height; # perl5 visibility rules
> };
But no $ for the keys of %ws.
%ws {
print ^heigh
Then assignment is the gatekeeper?
But what information will the lvalue sub have for deciding what to
make lvaluable?
> "DC" == Damian Conway <[EMAIL PROTECTED]> writes:
DC> And I keep pointing out that this is only one aspect of lvalue subroutines.
DC> The point of an lvalue subroutine i
"David L. Nicol" wrote:
>
> What if perl6 kept it as the default, but allowed any class
> to override the object->BOOLEAN accessor which will return
> um, a special TRUE and FALSE which only make sens in boolean
> contexts?
>
> Hopefully someone else can come up with a good example.
This is actu
As Graham pointed out, is an lvalue sub supposed to act like a tie or
like a variable.
If it acts like a variable it can't be a gatekeeper.
Hmm, what if the sub gets a chance to look at the value before acting.
Checks the value. If good returns a reference to the correct variable
to save it in.
We mostly can. This is really an echo of the "read-only, not constant"
idea from a while back. This way you can take references to them, for
instance. The compiler doesn't know where they will go.
Overloading the assign-to-me operator is faster than having a flag, you
never have to check it.
Jerrad Pierce wrote:
>
> Perl6 does not *have* to break anything, and certainly not everything.
> The prime directive should be not to break things unless necessary.
> Translation should not be a fall-back panacea. And it surely isn't perfect...
Actually, this is false. If Perl 6 worked just like
Damian Conway wrote:
> Actually, no I wouldn't.
> I'd be happier if it were more explicit.
>
> How about:
>
> keys %professors = ^a->name cmp ^b->name;
>
> keys %students = $$students{^1}{GPA} <=> $$students{^0}{GPA} };
>
> ;-)
>
> Damian
Okay, let's see what you've got here
> Lets use hats again then.
>
>%ws{
>print ^$height; #prints $ws{height}
>print $height; # perl5 visibility rules
>};
>
> AFAIK, the entirety of %name{something here} is unplowed ground, as
> far as perl syntax goes.
For good reason, A
"David L. Nicol" wrote:
>
> I like very much a print() that returns the value of what you
> printed rather than success. I am always needing to define
> littly intermediate temporaries so I can insert debugging code
> inside huge, tortuous expressions.
I think this is an excellent idea independ
Jeremy Howard wrote:
>
> This is one of those
> few cases where VB has nicer syntax--within a 'with' block you have to
> precede a property name with '.' to get the with block scope:
>
> dim height as double
> dim ws as new Excel.worksheet // 'worksheet' has a 'height' property
>
> with
> This message is intended to remind us all that the deadline for this
> working group is _tomorrow_.
Not so fast!
This is not true anymore. I sent an email to K. requesting all the
current sublists be made permanent. She agreed. Here's the list of
*permanent* sublists:
-io = ALL I/O
David L. Nicol wrote:
> Yes, absolutely, about the semantics.
>
> About the syntax, how about just in a block behind %HASHNAME?
>
> (as long as it doesn't use $a and $b, of course )
> (or if the insta-sort thing needs "sort" written in and this doesn't)
>
> %record{
>
> $something_new = 3; # just
Think about deadlock, extra overhead, and time taken to take the lock.
If a set of variables should be locked as a unit only one mutex should
be assigned.
What to do about overlapping members
> "DLN" == David L Nicol <[EMAIL PROTECTED]> writes:
DLN> I wrote a transaction-enabled data
512 byte pages, stored on a permanent device and paged
in as required, for everything
--
David Nicol 816.235.1187 [EMAIL PROTECTED]
Does despair.com sell a discordian calendar?
Jonathan Scott Duff wrote:
>
> On Tue, Aug 15, 2000 at 05:47:53PM -0600, Nathan Torkington wrote:
> > I want
> > @result = @a || @b;
> > to be like:
> > (@result = @a) or (@result = @b);
> >
> > That's what all my students keep expecting it to mean.
>
> And that's what I keep wishing it mea
Yes, absolutely, about the semantics.
About the syntax, how about just in a block behind %HASHNAME?
(as long as it doesn't use $a and $b, of course )
(or if the insta-sort thing needs "sort" written in and this doesn't)
%record{
$something_new = 3; # just set $rec
My last message mentioned planned changes to RFCs. Lest anyone
should worry that I'm going to spring major surprises as this group's
time comes to an end, I'd like to mention that every change reflects
things that have been discussed here. Probably the only thing that
might surprise some peop
Perl5 has well defined but sometimes confusing "truth."
This is a weakness of it.
What if perl6 kept it as the default, but allowed any class
to override the object->BOOLEAN accessor which will return
um, a special TRUE and FALSE which only make sens in boolean
contexts?
That way there's
Tony Olekshy wrote:
> Also, the stuff going on in perl6-language-errors assumes a core
> Exception class, for use by "use Fatal (:all)" or whatever. Since
> this is, I believe, the first case of a "built-in" Perl class, there
> may be implications.
>
> Yours, &c, Tony Olekshy
I believe you ar
On Thu, 17 Aug 2000, John McNamara wrote:
> On Wed, Aug 16, 2000 at 11:42:20AM -1000, Tim Jenness wrote:
> > What about:
> >
> > for (0..$#array) {
> > print $array[$i], " is at index ", $i, "\n";
> > }
> >
> > I use that whenever I need to loop over indices of two arrays at once.
>
>
>
Graham Barr wrote:
> > This would
> > appear largely transparent to the user, right up until they tried to do
> > isa() or ref() tests on the object.
>
> But that is the catch. Now if the language was to give us a way to support
> both in the same package in an efficient way, so much the better
Glenn Linderman wrote:
>
> "David L. Nicol" wrote:
>
> > What I was suggesting was, if you want to overload the
> > autoloading of something, it could be done with "catch"
> > instead of rewriting the ::OVERLOAD procedure, for that
> > module.
>
> But none of the currently proposed exception handl
"David L. Nicol" wrote:
>
> sub openrecord{
> my $counter, $RFN;
> while( 1){
> -r ($RFN = &GetRecordFileName) and last
> ++$counter > 6 and return undef;
> };
> open REC, "$RFN";
> ...
> }
Depend
What if its a method of anything in an array? $_ is already
a reference to the object on the array in for loops rather
than a copy of it. What if we make change be not something about
for loops, but about anything in an array?
print "The index, in its array, of <<$_>> is $CORE::ARRAY
Peter Scott wrote:
> Tony Olekshy wrote:
> >Peter Scott wrote:
> > > Tony Olekshy wrote:
> > > >
> > > > try { TryToFoo; }
> > > > catch { TryToHandle; }
> > > > finally { TryToCleanUp; }
> > > > catch { throw "Can't cleanly Foo."; };
> > > >
> > > > In our
> >>%professors{ $a->name cmp $b->name };
> >>
> >>%students{ $$students{$b}{GPA} <=> $$students{$a}{GPA} };
> >
> > These already mean something. Please don't "special-case" them.
>
> No they don't.
Apologies. You're quite correct.
> > Isn't this b
"Christopher J. Madsen" wrote:
> Why not use an explicit counter instead? Something like
>
> foreach $item $index (@array) {
>
> (This is a syntax error in Perl5.)
Why not use an explicit perl5 counter?
my $index;
foreach $item (@array){ $index++;
print $i
This message is intended to remind us all that the deadline for this
working group is _tomorrow_. I feel we've hashed out most of the
details of the various proposals and that any other issues will be
minor or can be settled closer to implementation time.
I realize I've spewed a whole lot o
Nate the prolific Perl6 RFC producer and commentator wrote:
> I don't think suggesting that we eliminate globals altogether is a good
> or feasible idea. It's an unnecessary crutch. They are useful in many
> circumstances.
So here's my order of preference:
1) Eliminate dynamic variables entire
Damian Conway wrote:
>
>>%professors{ $a->name cmp $b->name };
>>
>>%students{ $$students{$b}{GPA} <=> $$students{$a}{GPA} };
>
> These already mean something. Please don't "special-case" them.
No they don't.
[david@nicol1 perl]$ perl -le '%nums = (1..20); print %nums{1}'
C
> Yes, it almost seems like there is no language visible difference
> between having the variable exist in the outer scope (file) and having
> it exist in the outermost scope in which it is referred to. Please
> correct me if you are thinking of one.
No, I can't see one. Not if you're auto-sco
I'd like to say that I whole-heartedly endorse the sentiments expressed in
this RFC (and *not* just because it likes my book! ;-)
It will definitely underpin my thinking when I finally put together my
own OO RFCs.
Well done, John.
Damian
I wrote a transaction-enabled database in perl 5, using fork()
for my multithreading and flock() for my mutexes. It continues
to work just fine.
Threading gives us mutexes. Are you just saying that
every variable should have its own mutex, and perl's = assignment
operator should implicitly se
> > print sub {
> > return < > Dear $_[0]
> > Your tuition is now due. Please send in a payment of at least
> > $_[1].
> > SPAM
> > }
>
> What does the second one mean, then? Doesn't
>
> print sub { ... }
I like very much a print() that returns the value of what you
printed rather than success. I am always needing to define
littly intermediate temporaries so I can insert debugging code
inside huge, tortuous expressions.
I don't know if C(>"print me"<) is it though.
Did you take a look at RFC 6
Could also use this for
foreach $item $key ( %hash ) {
print "$item is indexed by $key\n";
}
"Christopher J. Madsen" wrote:
> I don't see why this should be an implicit counter. This (might)
> cause extra work for every foreach loop in every program (depending on
> how foreach is impl
Jonathan Scott Duff wrote:
> On Thu, Aug 17, 2000 at 03:30:09PM -0700, Jon Ericson wrote:
> > Nathan Wiger wrote:
> > >3. Can you support here documents with this syntax?
> >
> > I haven't thought about this yet, but you can always use print.
>
> Should be the same:
>
> ><<'FOO'
>
On Thu, Aug 17, 2000 at 08:20:35PM +, Nick Ing-Simmons wrote:
> Simon Cozens <[EMAIL PROTECTED]> writes:
> >>BEGIN {$c_code = &c_code_generator()}
> >>use Inline C => $c_code; # will die if code doesn't compile
> >>myfunc1();
> >>
> >>greet('Ingy');
> >>
I've been wanting to respond to these issues for the past two days,
but I've stopped short while I tried to consider everything.
This email dealt with making lexical variables default to being
available at the outermost scope (file). I'm not sure that's what
people usually mean when they th
> internally, how to do it:
>
> ASSIGNMENT, as in, Change-my-values-w/o-changing-my-type,
> is in the vtable for the object.
>
> When an object becomes constant, its ASSIGNMENT function gets
> replaced with
>
> $heres_what_it_gets_replaced_with=sub{
> throw "ERROR-ASSIGNMENT-TO-CONSTANT"
> };
>
>
On 8/17/00 5:36 PM, Perl6 RFC Librarian wrote:
> NOTE: these and other examples assume Highlander Variables (RFC 9)
> where '$mage', '@mage' and '%mage' all refer to different "views" of
> the same variable, rather than different variables as in Perl 5.
> Otherwise read '@mage' as '@$mage' and '%m
> This RFC proposes that the existing C<..> operator produce a lazily
> evaluated list. In addition, a new operation C<:> is proposed that allows
> for the generation of lazily evaluated lists based on any Perl expression.
Llama 2nd ed. calls ? the "lazy operator" w/in regexes, in my lazy props
I was just sitting here thinking over all these issues and making
various responses (as well as adjustments to my mental model for RFC
106 v2).
With the radical proposal of eliminating dynamic variables that RFC
106 includes (as an option! Don't get excited; read the RFC first!),
I've demon
internally, how to do it:
ASSIGNMENT, as in, Change-my-values-w/o-changing-my-type,
is in the vtable for the object.
When an object becomes constant, its ASSIGNMENT function gets
replaced with
$heres_what_it_gets_replaced_with=sub{
throw "ERROR-ASSIGNMENT-TO-CONSTANT
> [EMAIL PROTECTED] (Nathan Wiger) wrote on 14.08.00 in
> <[EMAIL PROTECTED]>:
>
>> Well, lexical variables don't belong to any package in Perl. They're not
>> in the symbol table, hence why others can't mess with them. That's why a
>> "my $var" is different from a "$pkg::var". The latter gets i
Decklin Foster wrote:
>
> [replying from here since this is the only way I received it]
>
> > "Myers, Dirk" wrote:
> > >
> > > $line/pattern/ ;
> >
> > > /pattern/ ($line) ;
>
> I don't think these should be changed. Here's how I tend to pronouce
> things:
>
> $x = 'foo'; #
Nathan Wiger wrote:
>
> We're getting deluged with RFC's and emails. We should start thinking
> "will this RFC or idea *add value* to Perl 6?". If not, and it just
> makes something work differently, it _might_ not be worth an RFC.
I disagree completely. For one thing, there's no such thing as P
Perl6 RFC Librarian wrote:
> The new C<$DEFIN> accomplishes a similar thing, but with
> input. Currently, the special <> filehandle acts on one of
> two things, either C<@ARGV> or (if C<@ARGV> is
> empty).
This is not strictly true. <> is shorthand for . ARGV is the
special filehandle that ope
Damian Conway wrote:
> This:
>
> print < Dear ^name:
> Your tuition is now due. Please send in a payment of at least
> ^minumum.
> SPAM
>
> already means:
>
> print sub {
> return < Dear $_[0]
> Your tuition is now
> "RA" == Russ Allbery <[EMAIL PROTECTED]> writes:
RA> Damien Neil <[EMAIL PROTECTED]> writes:
>> Arrays are ordered. Hashes are not. Sure, you can iterate over a hash,
>> but add an element to one and you can change the order of everything in
>> it.
RA> Formally, I believe it's
> Perl6 RFC Librarian writes:
>> The chief instance where Perl5 requires dynamic variables is in the
>> case of package globals.
>
> I think this is a bad idea (so I'm glad you made it optional).
Thanks for the feedback, Nat.
I figured the idea would meet with resistance. Really, since the
[replying from here since this is the only way I received it]
> "Myers, Dirk" wrote:
> >
> > $line/pattern/ ;
>
> > /pattern/ ($line) ;
I don't think these should be changed. Here's how I tend to pronouce
things:
$x = 'foo'; # "x gets foo"
/bar/;# "match on bar"
On Thu, Aug 17, 2000 at 03:30:09PM -0700, Jon Ericson wrote:
> Nathan Wiger wrote:
> >3. Can you support here documents with this syntax?
>
> I haven't thought about this yet, but you can always use print.
Should be the same:
><<'FOO'
blah
blah
FOO<
> >
>Well, fileobjects are already in Perl 5. Most people just don't use them
>by default. But as TomC pointed out, in Perl 5 you can do this:
> open $fh, "$file";# if 'use FileHandle'
I do use them, occasionally...
>Already. These proposals just make that the default.
No the "default" is what
At 05:18 PM 8/17/00 -0500, David L. Nicol wrote:
>Peter Scott wrote:
>
> > >Maybe $! becomes an alias for anything that gets thrown
> >
> > Actually it looks like $@ is doing that at the moment. *Confused*
>
>Make them all writable, then we can make user-defined errors seem
>to be whatever we w
At 09:13 PM 8/16/00 -0600, Tony Olekshy wrote:
>Peter Scott wrote:
> >
> > Tony Olekshy wrote:
> > >
> > > try { TryToFoo; }
> > > catch { TryToHandleFailure; }
> > > finally { TryToCleanUp; }
> > > catch { throw "Can't cleanly Foo."; };
> > >
> > >In our pr
In message <[EMAIL PROTECTED]>
Perl6 RFC Librarian <[EMAIL PROTECTED]> wrote:
> Rather than indicating that lazy evaluation is required by the
> addition of incomprehensible syntactic hints, a "lazy array context"
> is indicated by the presence of the new keyword C.
I think I've actual
In message <[EMAIL PROTECTED]>
Perl6 RFC Librarian <[EMAIL PROTECTED]> wrote:
> A "sort function" will need to be added into the list of magics
> maintained for every associative array.
>
> A set of macros in terms of sort will need to be defined which
> replace keys, values, and each f
Well, ok, one "language" is just a subset of the other (guess I didn't
communicate that), but they are still distinct and still cause for
concern.
However, I think that if we're going to write this DFA at all, then the
user SHOULD have the choice of using it for normal regex matchs, by
specify
On Thu, 17 Aug 2000, John Porter wrote:
> Huh? They need to be "globals", because the "with" mechanism
> is going to have to be able to write them into a symbol table.
> You can't do this with lexicals. (Well, maybe that'll be different
> in perl6?)
Well, if you're using the HOF nota
>> Furthermore, in the "more rope" department, it might be possible to make
>> local() work on my() variables this way.
>
> I'm still unsure if this is a good thing. I think it is, but it's worth
> some pondering.
>
> -Nate
>
In the programming languages class I took last year, we wrote an
inte
Perl6 RFC Librarian wrote:
> With C<$DEFERR>, all error functions are set to act on it
> instead of C<$STDERR> by default. So, the Perl 6 version
> of the above is replaced by a single, simple line of code
> at the top of your main program:
>
>$DEFERR = $ERRORLOG unless $have_a_tty;
open S
At 09:12 PM 8/16/00 -0600, Tony Olekshy wrote:
>Executive summary: I no longer want catch blocks to "daisy chain"
>after a exception is thrown in a catch block. Thanks to everyone
>who has helped me see the light on this.
I'm not sure what you mean by "daisy chain". I have been taking it to mean
On Thu, Aug 17, 2000 at 03:10:44PM -0700, Steve Fink wrote:
> My proposal would be what I implemented for perl5 a while back (Sarathy
> didn't dislike it, but wasn't convinced enough to put it in): all
> dereferencing can be done with ->.
>
> $x->@ is the same as @$x
> $x->% is the same as %$x
>
> I vehemently disagree with this filehandle object nonsense.
> This is Perl, not Java, not Python. Everyone together Purrl... :-P
Well, fileobjects are already in Perl 5. Most people just don't use them
by default. But as TomC pointed out, in Perl 5 you can do this:
open $fh, "$file";# i
Stephen P. Potter wrote:
> Lightning flashed, thunder crashed and "Jeremy Howard" <[EMAIL PROTECTED]>
whispered:
> | No. They are lazily evaluated and require special optimisations to allow
>
> I don't completely understand this whole lazy evaluation, so I'm confused
> how these functions would wo
Nathan Wiger wrote:
>
> > >"Print this line.\n"<;
>
> Some questions:
>
>1. How do you specify alternate filehandles to output to?
> select() doesn't count for the purposes of this question.
It's a shortcut, not a replacement. Rumors of select's death are
greatly exaggerated.
>
Karl Glazebrook wrote:
>
> Ariel Scolnicov wrote:
> >
> > Karl Glazebrook <[EMAIL PROTECTED]> writes:
> >
> > [...]
> >
> > > o Why do I think perl has too much line noise? Because of code like this:
> > >
> > > @{$x->{$$fred{Blah}}}[1..3]
> >
> > This is indeed horrible. However, I fail to se
Chris Nandor <[EMAIL PROTECTED]> writes:
> Here are some comments from Matthias Neeracher, the MacPerl author, and
> a few comments from me.
Cool, thanks.
>> Is it? I thought DOS/Windows uses 1900, but I don't know what Perl on
>> these platforms does.
My understanding is that the native epoch
Peter Scott wrote:
> >Maybe $! becomes an alias for anything that gets thrown
>
> Actually it looks like $@ is doing that at the moment. *Confused*
Make them all writable, then we can make user-defined errors seem
to be whatever we want.
Or leave them the hell alone and introduce a new var
Nice thought.
Actually, this or something like this might be helpful in maintainting
invariants in the face of exceptions.
Though this is a tough problem especially in the face of threads.
Though versioned variables may be able to remove most of the locking
issues and move it down into the commi
Ted Ashton wrote:
>
> > But the most direct way to measure how well the
> > language slides into people's heads is by seeing how hard it is for them
> > to get the hang of it.
>
> Nope. I've yet to be convinced that "fits in your head" is the same as
> "went in easily". Hang
Here are some comments from Matthias Neeracher, the MacPerl author, and a
few comments from me.
>To: Chris Nandor <[EMAIL PROTECTED]>
>Subject: Re: Fwd: RFC 99 (v2) Standardize ALL Perl platforms on UNIX epoch
>Date: Wed, 16 Aug 2000 07:31:25 +0200
>From: Matthias Ulrich Neeracher <[EMAIL PROTECT
In reply to your message from the not too distant future: next Thursday AD
Reply-to: [EMAIL PROTECTED]
Return-receipt-to: [EMAIL PROTECTED]
Organization: a) Discordia b) none c) what's that?
Content-Typo: gibberish, charset=ascii-art
Date: Thu, 17 Aug 2000 18:05:33 EDT
From: Jerrad Pierce
>[1] T
> We need to get a new keyword for defining such a variable, I think
> "transaction" is too long, we could use "safe" for this reason.
The proposal looks good. But isn't this more a language issue at this
point? Seems like we'll have to figure out the behavior we want first.
Also, "safe" i
I don't see why this should be an implicit counter. This (might)
cause extra work for every foreach loop in every program (depending on
how foreach is implemented).
Why not use an explicit counter instead? Something like
foreach $item $index (@array) {
print $item, " is at index ", $
At 12:51 PM 8/17/00 -0700, Damien Neil wrote:
>Hmm. It just occurred to me that you could combine your idea with
>exceptions quite nicely: All core functions throw exceptions on
>error, but only when called in a void context. (As well as, perhaps,
>when a given pragma is in effect.) This way, o
1 - 100 of 214 matches
Mail list logo
