On 9/1/05, Rafael Garcia-Suarez <[EMAIL PROTECTED]> wrote:
> I just commited into bleadperl a patch that implements this :
>
> $ ./perl -e 'no 5'
> Perls since v5.0.0 too modern--this is v5.9.3, stopped at -e line 1.
> BEGIN failed--compilation aborted at -e line 1.
>
> That is, the e
On Mon, Jun 2, 2008 at 6:50 PM, Larry Wall <[EMAIL PROTECTED]> wrote:
>* Exception handlers run in the lexical context of the block being
>tried.
>* Exception handlers run in the dynamic context of the code that is
>failing.
the first seems dangerous, esp. considering the
On Wed, Jun 4, 2008 at 7:21 AM, Mark J. Reed <[EMAIL PROTECTED]> wrote:
> The catch block is lexically contained within the try block, so the
> inviolate nature of the curlies remains intact.
thank you.
the general magic level of
the other slots in *_, is it not?
--
David Nicol /
So is he going to backport his representational ideography to
the operators of perl 5.8?
Darren Duncan wrote:
Mark Lentczner has just (on May 26/28) created a useful/humerous
graphical diagram of the 100+ operators in the Perl 6 language, designed
to look like the periodic table of atomic element
Herein are drafty grumblings.
Part of quitting smoking is that my hubris has gone back up.
Here are critical first-impression notes on Apo3. Praise has
been eliminated to save space.
http://www.perl.com/pub/a/2001/10/02/apocalypse3.html?page=1
> Operator precedence should be as simple
Michael G Schwern wrote:
> Binary ;
>
> This worries me. Giving ; two meanings makes basic language parsing
> harder, which would be fine if there was a big payoff, but there's
> not. Just making shorthand for [[1,2,3],[4,5,6]] doesn't seem worth
> it. What am I missing here?
What you migh
Damian Conway wrote:
> David Nicol wrote:
>> Hear ye, hear ye, Ming of Mongo has declared!
>
> I really hope I'm just missing the implicit smiley there.
What you're missing is me wracking my memory to remember what
Dr. Zharkov called his tunneling craft that
David wrote:
> Damian Conway wrote:
> > NaN is dead.
>
> > Except perhaps under a C pragma of some kind, in which case it
> > would be a proper IEEE Norweigian Blue NaN.
>
> which merely redifines the discussion to, how does the IEEENBNaN
> behave under various cir
N, but numerically always compares
to false, so the conditional in the example could CLEARLY be written
while $inflation ne NaN;
--
David Nicol 816.235.1187
1,3,7-trimethylxanthine
($realpart, $imaginarypart) = /^\b(\d*\.?\d+)\+(\d*\.?\d+)i\b/
and "123indigo" does not match that.
--
David Nicol 816.235.1187
1,3,7-trimethylxanthine
http://www.cl.cam.ac.uk/~cu200/Prover/index.html
unicode.
We are planning on having an easy way to add printf conversions,
are we not?
--
David Nicol 816.235.1187
1,3,7-trimethylxanthine
unitialized variables.
--
David Nicol 816.235.1187
1,3,7-trimethylxanthine
Original Message
Return-Path: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
Received: (qmail 14099 invoked from network); 14 Feb 2002 22:51:43 -
Received: from eros.cs.jhu.edu (128.220.223.245)by hilbert.umkc.edu with SMTP; 14 Feb
2002 22:51:43 -
Received: from e
The thought process went something like this.
In a world of distributed perl data, we want an
expression like
foreach (grep { $_->{smoker} and $_->{age} > 18 } @Subscribers){
$->send($Cigarette_Advertisement)
}
to do the filtering on the machine that holds the s
For example
for( initialize ; test ; increment ) body
means
{initialize ; while (test) {body ; increment }}
;
thanks
--
David Nicol, independent consultant and contractor 312 587
2868
"For every old blackboard there are now hundreds of new electronic
computers"
push @arr, $_;
$_;
}
And this might even just be a special case that perl6 array-FETCH is
supposed to know about. (or create a LAST tie operator.)
The range specs that know their own length without flattening (see
a few paragraphs prev. in apo6) and counting would know
the slice()
semantics; what if
$last = @array[-1]
always worked?
--
David Nicol, independent consultant and contractor
perl -Mcoroutine0 -e'$c=new coroutine0 VARS=>[],BODY=>q"YIELD 74;
YIELD 65;YIELD 80;YIELD 72; YIELD 10;";for(;;){print chr(&$c||die)};'
I think a range object needn't ever expand itself. Consider:
@Floor = (0..Inf,-Inf..-1);
--
"Life is like a sewer: what you get out of it
depends on what you put into it." -- Hen3ry
leness standard which has appeared in
the ensuing years)
david nicol
21 matches
Mail list logo
