On Thu, 24 Jun 2004, Luke Palmer wrote:
defaults. For example, using Perl5 syntax, here's what I mean:
^^
^^
[snip]
perl -e 'unlink *.txt :v'
Well it's certainly not going to be that, since the glob
On Thu, 24 Jun 2004, Luke Palmer wrote:
However I wonder if an implicit stack could be provided for return()s into
void context. It is well known that currently split() in void context has
[snip]
To be honest, I have no idea what you're asking for. Might you explain
in a little more
Michele Dondi writes:
On Thu, 24 Jun 2004, Luke Palmer wrote:
However I wonder if an implicit stack could be provided for return()s into
void context. It is well known that currently split() in void context has
[snip]
To be honest, I have no idea what you're asking for. Might you
On Tue, 29 Jun 2004, Luke Palmer wrote:
1;
$_='foo bar baz';
split;
# @STACK now is (1, 'foo', 'bar', 'baz');
I can imagine some uses for that...
Sick... and... wrong. :-)
:-(
Not only would it mess with what things have to do in void context, it
would fudge up the
[EMAIL PROTECTED] (Luke Palmer) writes:
$_='foo bar baz';
split;
# @STACK now is (1, 'foo', 'bar', 'baz');
I can imagine some uses for that...
Sick... and... wrong. :-)
Not only would it mess with what things have to do in void context, it
would fudge up the garbage collector
On Tue, 29 Jun 2004, Michele Dondi wrote:
for qw/foo bar baz/ { .subst /.(.*)/, {.1};; }
^
Err, I meant $1, and even then I'm not really sure it is (well, would
be correct!)
Michele
--
You know, you would learn a lot more mathematics from a
Austin Hastings [EMAIL PROTECTED] writes:
Of course, how hard can it be to implement the .parent property?
.parent and also .children, plus .moveto and .remove (which doesn't
actually destroy the object but sets its parent to undef, basically,
cleaning up the .children property of its parent),
On Tue, 29 Jun 2004, Jonadab the Unsightly One wrote:
Austin Hastings [EMAIL PROTECTED] writes:
Of course, how hard can it be to implement the .parent property?
.parent and also .children, plus .moveto and .remove (which doesn't
actually destroy the object but sets its parent to undef,
Dan Sugalski [EMAIL PROTECTED] writes:
Hmm. Suppose that I have a system that is friendly to 80 byte
records. I want to output meaningful strings, so I want to
partition a buffer into 80-ish byte substrings, but preserve any
graphemes (i.e., store the data in a legible format).
How would I
Austin Hastings [EMAIL PROTECTED] writes:
A couple of alternatives:
substr.bytes($string, 2, 4) = $substitute;
Well, that's arguably better than bsubstr.
substr($string.bytes, 2, 4) = $substitute;
I could live with that, although it doesn't allow mixing units.
(Someone will pop in here
John Williams [EMAIL PROTECTED] writes:
$b = 'a';
my $b ='b' , print $b\n;
print $b\n;
Which seems to show that the my $b doesn't actually come into
scope until the end of the statement in which it is defined.
The comma operator doesn't guarantee order of operation because it's
The Perl 6 Summary for the week ending 2004-06-27
What's this? No! It can't be! It's a *weekly* Perl 6 Summary. What is
the world coming to?
Sorry, I can't answer that one, so I'll tell you what's been happening
this week in perl6-internals.
Bignums, licenses, pie
As you
The Perl 6 Summarizer wrote:
Mmm... Pie-thon
Dan reminded everyone of the URL of the benchmark that's going to be run
for the Pie-thon. If Parrot doesn't run it faster than the C
implementation of Python, then Dan's going to get a pie in the face and
he'll have to spring for a
--- Jonadab the Unsightly One [EMAIL PROTECTED] wrote:
Have the implications of the bytes/codepoints/graphemes/woohickies
distinction for the regular expression engine been discussed already?
Not enough.
One of my current clients just rolled on to redhat 9, and what a
steaming pile of
I must say I've still not read all apocalypses, and OTOH I suspect that
this could be done more or less easily with a custom function (provided
that variables will have a method to keep track of their history, or, more
reasonably, will be *allowed* to have it), but I wonder if Perl6 may
include a
Juerd [EMAIL PROTECTED] writes:
substr($string, 2 but graphemes, 4 but bytes);
I think but even makes sense, if substr defaults to something.
That could be combined with a smart substr that only needs the units
once (err, only needs a position object for one of the args) and knows
how to
Michele Dondi wrote:
I must say I've still not read all apocalypses, and OTOH I suspect that
this could be done more or less easily with a custom function (provided
that variables will have a method to keep track of their history, or, more
reasonably, will be *allowed* to have it), but I
On Tue, Jun 29, 2004 at 08:34:16AM -0700, Austin Hastings wrote:
This has no direct bearing on p6l, since performance is a p6i issue.
But perhaps in the interests of performance as well as hackery we
should explicitly provide some sort of variant regex behavior:
/a./ :bytes
/a./
Rafael Garcia-Suarez wrote:
Michele Dondi wrote:
I must say I've still not read all apocalypses, and OTOH I suspect that
this could be done more or less easily with a custom function (provided
that variables will have a method to keep track of their history, or, more
reasonably, will be *allowed*
Mark A. Biggar skribis 2004-06-29 9:07 (-0700):
Besides we already have MTOWTDI with local() and hypotheticals.
I thought temp replaced local. If not, how do they differ? (is temp for
lexicals, local for globals (and why would that make sense?))
Juerd
Sorry I did mean temp.
--
Mark Biggar
[EMAIL PROTECTED]
-- Original message --
Mark A. Biggar skribis 2004-06-29 9:07 (-0700):
Besides we already have MTOWTDI with local() and hypotheticals.
I thought temp replaced local. If not, how do they differ? (is temp
On Tue, 29 Jun 2004, Rafael Garcia-Suarez wrote:
Difficulties: define history of a function w.r.t. threads; closures;
and system side-effects (writing to files, locking them etc.)
On Tue, 29 Jun 2004, Mark A. Biggar wrote:
Besides we already have MTOWTDI with local() and hypotheticals.
On Tue, 29 Jun 2004 10:52:31 -0400, Jonadab The Unsightly One
[EMAIL PROTECTED] wrote:
People who think in terms of statements often get mixed up when they
put complex expressions in void context, expecting them to be treated
as statements. print(2+3)*7; is another example. Perl doesn't have
- Original Message -
From: Luke Palmer [EMAIL PROTECTED]
Date: Tuesday, June 29, 2004 6:13 am
Subject: Re: A stack for Perl?
1;
$_='foo bar baz';
split;
# @STACK now is (1, 'foo', 'bar', 'baz');
To boot, I can't think of a way to implement that in currently-defined
Dan Sugalski [EMAIL PROTECTED] writes:
Sure, no big deal. Also, don't forget the trival matter of moving
from a class-based object system
No, the object system in question is still class-based. The object
forest is orthogonal to that.
--
$;=sub{$/};@;=map{my($a,$b)=($_,$;);$;=sub{$a.$b-()}}
Michele Dondi [EMAIL PROTECTED] writes:
I must say I've still not read all apocalypses, and OTOH I suspect
that this could be done more or less easily with a custom function
(provided that variables will have a method to keep track of their
history, or, more reasonably, will be *allowed* to
Jonadab the Unsightly One writes:
Michele Dondi [EMAIL PROTECTED] writes:
I must say I've still not read all apocalypses, and OTOH I suspect
that this could be done more or less easily with a custom function
(provided that variables will have a method to keep track of their
history, or,
Michele Dondi writes:
On Tue, 29 Jun 2004, Rafael Garcia-Suarez wrote:
Difficulties: define history of a function w.r.t. threads; closures;
and system side-effects (writing to files, locking them etc.)
On Tue, 29 Jun 2004, Mark A. Biggar wrote:
Besides we already have MTOWTDI
28 matches
Mail list logo