Hi everyone,
I wonder: why does take inside a gather structure returns undef?
I think it would be nicer if it could return the taken value, so that,
for example one can write something like:
say take 2
or like:
while cond($n) {
my $res = compute($n)
$n /= take($res)
}
there is a reas
gabriele (>):
I wonder: why does take inside a gather structure returns undef?
I think it would be nicer if it could return the taken value, so that,
for example one can write something like:
say take 2
or like:
while cond($n) {
my $res = compute($n)
$n /= take($res)
}
there is a
Parrot Bug Summary
http://rt.perl.org/rt3/NoAuth/parrot/Overview.html
Generated at Mon Jan 29 14:00:09 2007 GMT
---
* Numbers
* New Issues
* Overview of Open Issues
* Ticket Status By Version
* Requestors with m
i spent some time with PDD22 this week. i've started writing tests for
the ParrotIO object, which you'll find in the attached patch. you'll
also find some notes i've made both in the test file, and in the spec.
i find writing spec-based tests to be extremely enlightening. the act
of writing code
Author: larry
Date: Mon Jan 29 10:39:25 2007
New Revision: 13543
Modified:
doc/trunk/design/syn/S04.pod
Log:
Note that take is intended to work en passant as suggested by gabriele renzi++
Also clarified that gather provides a void context to its victim.
Modified: doc/trunk/design/syn/S04.pod
Author: larry
Date: Mon Jan 29 10:45:26 2007
New Revision: 13544
Modified:
doc/trunk/design/syn/S04.pod
Log:
Minor cleanups
Modified: doc/trunk/design/syn/S04.pod
==
--- doc/trunk/design/syn/S04.pod(original)
On Mon, Jan 29, 2007 at 10:39:27AM -0800, [EMAIL PROTECTED] wrote:
> +Because C evaluates its block or statement in void context,
> +this typically causes the C statement to be evaluated in void
> +context. However, a C statement that is not in void context
> +gathers its arguments I and also retu
On Mon, Jan 29, 2007 at 10:01:08PM +0200, Gaal Yahas wrote:
> > +Because C evaluates its block or statement in void context,
> > +this typically causes the C statement to be evaluated in void
> > +context. However, a C statement that is not in void context
> > +gathers its arguments I and also ret
On Mon, Jan 29, 2007 at 10:08:34PM +0200, Gaal Yahas wrote:
> On Mon, Jan 29, 2007 at 10:01:08PM +0200, Gaal Yahas wrote:
> > > +Because C evaluates its block or statement in void context,
> > > +this typically causes the C statement to be evaluated in void
> > > +context. However, a C statement t
Author: larry
Date: Mon Jan 29 14:06:49 2007
New Revision: 13545
Modified:
doc/trunk/design/syn/S04.pod
Log:
Clarifications requested by gaal++.
Modified: doc/trunk/design/syn/S04.pod
==
--- doc/trunk/design/syn/S04.
On Mon, Jan 29, 2007 at 01:22:49PM +0100, Carl Mäsak wrote:
: gabriele (>):
: >I wonder: why does take inside a gather structure returns undef?
: >I think it would be nicer if it could return the taken value, so that,
: >for example one can write something like:
: >
: > say take 2
: >
: >or like:
hello people!
I'm really interested in porting parrot to PDA (well, PocketPC at least).
some days ago I stumbled upon CeGCC (a cross compiler for PocketPC),
which is basically a windows port of gcc (both cygwin and mingw32
flavours) that produces ARM executable code.
I started playing with i
On 1/26/07, Klaas-Jan Stol <[EMAIL PROTECTED]> wrote:
attached is a patch including the PIR language using PGE.
My earlier patch was not (yet) delivered, so I'm sending the zip'ed
version, which is much smaller.
great! this has been applied (with changes to make it cross-platform
friendly) as
# New Ticket Created by Jerry Gay
# Please include the string: [perl #41371]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41371 >
committed as docs/roles_responsibilities.pod in r16834, project team
members should review
On Mon, Jan 29, 2007 at 02:06:51PM -0800, [EMAIL PROTECTED] wrote:
> +The C function essentially has two contexts simultaneously, the
> +context in which the gather is operating, and the context in which the
> +C is operating. These need not be identical contexts, since they
> +may bind or coerce
Author: larry
Date: Mon Jan 29 16:05:40 2007
New Revision: 13546
Modified:
doc/trunk/design/syn/S04.pod
doc/trunk/design/syn/S06.pod
Log:
More infonuggets for gaal++.
Modified: doc/trunk/design/syn/S04.pod
==
---
On Jan 29, 2007, at 17:06 , [EMAIL PROTECTED] wrote:
+absense of context propagation by the optimizer). The value returned
Minor spelling nit: "absence"
--
brandon s. allbery[linux,solaris,freebsd,perl] [EMAIL PROTECTED]
system administrator [openafs,heimdal,too many hats] [EMAIL P
Author: larry
Date: Mon Jan 29 17:41:22 2007
New Revision: 13547
Modified:
doc/trunk/design/syn/S04.pod
Log:
typo from KF8NH++
Modified: doc/trunk/design/syn/S04.pod
==
--- doc/trunk/design/syn/S04.pod(origin
# New Ticket Created by Will Coleda
# Please include the string: [perl #41373]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41373 >
.. To replace the TODO'd one which relied on non-core Perl5 PMCs.
See t/pmc/threads.t
--
# New Ticket Created by Will Coleda
# Please include the string: [perl #41374]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41374 >
To replace removal of Perl PMCs* from core: still should test this
functionality.
See
Author: larry
Date: Mon Jan 29 21:05:36 2007
New Revision: 13548
Modified:
doc/trunk/design/syn/S02.pod
Log:
More clarifications requested by thom++.
Modified: doc/trunk/design/syn/S02.pod
==
--- doc/trunk/design/syn
21 matches
Mail list logo
