On Jun 27, Steve Fink said:
>On Jun-26, Jeff 'japhy' Pinyan wrote:
>> I am currently completing work on an extensible regex-specific parsing
>> module, Regexp::Parser. It should appear on CPAN by early July (hopefully
>> under my *new* CPAN ID "JAPHY").
>>
>> Once it is completed, I will be start
On Jun 27, Luke Palmer said:
>Jeff 'japhy' Pinyan writes:
>> I am currently completing work on an extensible regex-specific parsing
>> module, Regexp::Parser. It should appear on CPAN by early July
>> (hopefully under my *new* CPAN ID "JAPHY").
>>
>> Once it is completed, I will be starting work
On Sat, Jun 26, 2004 at 08:41:08PM -0400, Vsevolod (Simon) Ilyushchenko wrote:
> >The problem occurs because Devel::Cover overrides some of B::Deparse's
> >subs, but when you go calling them in a program it gets upset. The
> >solution is to only override the subs for as long as is necessary. The
On Jun-26, Jeff 'japhy' Pinyan wrote:
> I am currently completing work on an extensible regex-specific parsing
> module, Regexp::Parser. It should appear on CPAN by early July (hopefully
> under my *new* CPAN ID "JAPHY").
>
> Once it is completed, I will be starting work on writing a subclass tha
Jeff 'japhy' Pinyan writes:
> I am currently completing work on an extensible regex-specific parsing
> module, Regexp::Parser. It should appear on CPAN by early July
> (hopefully under my *new* CPAN ID "JAPHY").
>
> Once it is completed, I will be starting work on writing a subclass
> that matche
Alexey Trofimenko writes:
> AFAIR, I've seen in some Apocalypse that lexical scope boundaries will be
> the same as boundaries of block, in which lexical variable was defined.
Yep. Except in the case of routine parameters, but that's nothing new.
>
> so, my question is, what the scope of var
Alexey Trofimenko writes:
> On Thu, 24 Jun 2004 10:55:26 -0700, Larry Wall <[EMAIL PROTECTED]> wrote:
>
>
> >Well, any operator or function that knows how to call a closure can
> >function as a short-circuit operator. The built-in short-circuit
> >operators are a bit special insofar as they're a
"Leopold Toetsch" <[EMAIL PROTECTED]> wrote:
> 1) Python has a complex builtin class. So we'll need one too.
> * Create a complex PMC.
> * Parse complex constants '4j'
j? I've always used i as the imaginary unit, though I believe j is used
more in engineering fields ('cus they use i for cu
AFAIR, I've seen in some Apocalypse that lexical scope boundaries will be
the same as boundaries of block, in which lexical variable was defined.
so, my question is, what the scope of variables, defined in C and
C conditions?
in perl5:
my $a="first\n";
if (my $a="second\n") {print $a}
On Thu, 24 Jun 2004 10:55:26 -0700, Larry Wall <[EMAIL PROTECTED]> wrote:
Well, any operator or function that knows how to call a closure can
function as a short-circuit operator. The built-in short-circuit
operators are a bit special insofar as they're a kind of macro that
treats the right side
I'll be near Stuttgart (Germany) on the German Perl Workshop
http://www.perl-workshop.de on Tuesday.
leo
1) Python has a complex builtin class. So we'll need one too.
* Create a complex PMC.
* Parse complex constants '4j'
* Put these constants into the PBC?
2) We need a *array.sort (NCI) method(s)
That's kind of a PITA: The fixed/resizable array PMCs don't
have push/pop/unshift/shift ..
12 matches
Mail list logo
