Leopold Toetsch wrote:
Rod Adams <[EMAIL PROTECTED]> wrote:
Well
if 10 < $j < 1 { ... }
if 10 < $j { if $j < 1 { ... }}
Could easily wind up with the same opcodes.
No. In the first case $j is evaluated just once. In the second case it's
evaluated twice.
You're right. I just di
Rod Adams <[EMAIL PROTECTED]> wrote:
> Well
> if 10 < $j < 1 { ... }
> if 10 < $j { if $j < 1 { ... }}
> Could easily wind up with the same opcodes.
No. In the first case $j is evaluated just once. In the second case it's
evaluated twice.
leo
Rod Adams writes:
> Dave Whipp wrote:
>
> >Rod Adams wrote:
> >
> >>I do not believe that you can create a 'lazy junction'. But I don't
> >>recall the topic coming up before, so we'll have to wait for Damian
> >>to come back unless someone else knows for certain.
> >
> >
> >My understanding is t
> "RA" == Rod Adams <[EMAIL PROTECTED]> writes:
>>
>> My understanding is that all lists are conceptually
>> lazy. "any(2..Inf)" is perfectly valid.
>>
>>
RA> The list being fed into the junction can be lazy. But I believe that
RA> the list gets iterated over completely in the
Dave Whipp wrote:
Rod Adams wrote:
I do not believe that you can create a 'lazy junction'. But I don't
recall the topic coming up before, so we'll have to wait for Damian
to come back unless someone else knows for certain.
My understanding is that all lists are conceptually lazy.
"any(2..Inf)"
Sam Vilain wrote:
Rod Adams wrote:
I do not believe that is possible.
This is the "filtering" or "unification" behavior that people keep
wanting junctions to have, which they do not.
Aww! But what about all the great problems that could be expressed
with them? I know of two languages that consi
Rod Adams wrote:
I do not believe that you can create a 'lazy junction'. But I don't
recall the topic coming up before, so we'll have to wait for Damian to
come back unless someone else knows for certain.
My understanding is that all lists are conceptually lazy. "any(2..Inf)"
is perfectly valid.
Rod Adams wrote:
I do not believe that is possible.
This is the "filtering" or "unification" behavior that people keep
wanting junctions to have, which they do not.
Aww! But what about all the great problems that could be expressed
with them? I know of two languages that consider this to be a co
Terrence Brannon wrote:
I gave a talk on Perl 6 Junctions at the Thousand Oaks Perl Mongers
meeting last night
http://www.hcoop.net/~terry/perl/talks/p6-junctions/index.html
and two questions/desires came out of it:
1: will it be possible to know which element of a junction is
currently
I gave a talk on Perl 6 Junctions at the Thousand Oaks Perl Mongers
meeting last night
http://www.hcoop.net/~terry/perl/talks/p6-junctions/index.html
and two questions/desires came out of it:
1: will it be possible to know which element of a junction is
currently being used? E.g.:
10 matches
Mail list logo
