jerry gay wrote:
yes, '.local' in a macro should mean the same thing as '.local' in
pir.
You've got it exactly.
to confuse the matter further, '.local' in a macro currently
means "create a unique label."
kjs's proposal changes that to '.label'
local in pir and macro language means crea
Joshua Isom wrote:
.sub bar
.declare_my_locals(foo)
local_declare_my_locals_foo = 5
print local_declare_my_locals_foo
...
.end
Those aren't meant to be accessed outside the macro. And imcc adds a
number to it to make it hard to guess and there's no incentive to do
that.
The probl
Bob Rogers wrote:
All I am talking about is the equivalent of what "local $var" provides
for Perl 5, i.e. dynamically-scoped binding of scalar "package
variables."
Perl 5 locals and Perl 6 temps are quite different than Lisp special
variables. I don't immediately see a way to explain this any
On Oct 23, 2007, at 5:45 PM, Allison Randal wrote:
Klaas-Jan Stol wrote:
Hi, attached a document describing the current macro layer of IMCC.
On the proposed modifications to macros, I have reservations on the
automatic munging of .local variable names. Macros are simple
parameterized subst
# New Ticket Created by chromatic
# Please include the string: [perl #46761]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=46761 >
There's a segfault in t/dynpmc/dynlexpad_2.pir with the gcdebug core. It
happens at the e
# New Ticket Created by Will Coleda
# Please include the string: [perl #46757]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=46757 >
Getting a segfault on osx/86 in tcl's t/cmd_array.t test.
Thanks to chromatic's new gcde
> looks like all dutch to me.
>
Part of it is in English, (the abstract). The body of the paper is in
Dutch (and Javascript). The abstract is very positive towards Parrot.
>>
>>http://users.fulladsl.be/spb1622/pjs/scriptie.pdf
>
It's too bad that some of the energy being dissipated on pointless
r
Patch applied in r22436; ticket is resolved.
Patch applied in r22436 for $/ problem. Am still considering other
refinements per chromatic's suggestion.
The $/ problem was fixed in r22436; ticket is still open for other unit
tests.
Patch applied in r22436; ticket is once again resolved.
Patch applied in r22436; ticket is once again resolved.
On 10/23/07, Allison Randal <[EMAIL PROTECTED]> wrote:
> Klaas-Jan Stol wrote:
> > Hi, attached a document describing the current macro layer of IMCC.
>
> On the proposed modifications to macros, I have reservations on the
> automatic munging of .local variable names. Macros are simple
> parameteri
On Tue Oct 23 12:16:06 2007, [EMAIL PROTECTED] wrote:
> Hi,
>
> I clicked on the "Languages" link on the sidebar; in the past I've been able
> to see the list of languages that are currently targeting Parrot, but this
> page now contains no information whatsoever.
>
> Thanks!
> ~Brian DeVries
Fi
# New Ticket Created by "Brian DeVries"
# Please include the string: [perl #46751]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=46751 >
Hi,
I clicked on the "Languages" link on the sidebar; in the past I've been able
to
From: Allison Randal <[EMAIL PROTECTED]>
Date: Mon, 22 Oct 2007 19:16:37 -0700
Bob Rogers wrote:
>In what seems to have become an autumn tradition in the Parrot
> community, I am about to make my third annual attempt to implement
> Parrot support for what Common Lisp calls "s
Klaas-Jan Stol wrote:
Hi, attached a document describing the current macro layer of IMCC.
On the proposed modifications to macros, I have reservations on the
automatic munging of .local variable names. Macros are simple
parameterized substitutions. If someone includes a '.local' in a macro,
Author: allison
Date: Tue Oct 23 13:39:33 2007
New Revision: 22428
Modified:
trunk/docs/pdds/draft/pdd19_pir.pod
Log:
[pdd] Some basic structural shaping on PIR PDD, and answering some of the
review points.
Modified: trunk/docs/pdds/draft/pdd19_pir.pod
==
On Tue, Oct 23, 2007 at 12:40:17PM -0700, chromatic wrote:
> ... except don't break CONST_STRING across lines, because apparently icc
> can't
> count and won't compile.
>
> One might assume that being able to count is less of a burden than handling
> pointer math correctly, but I never took a
On Tuesday 23 October 2007 12:32:21 Allison Randal wrote:
> You will need to bundle up the 'sub' argument in a hash (the low-level
> equivalent of named arguments like 'initial_sub'). So, using your
> existing init_pmc, it'll be something like:
>
>void init_pmc(PMC* sub) {
> PMC *classobj
looks like all dutch to me.
-Original Message-
>From: Klaas-Jan Stol <[EMAIL PROTECTED]>
>Sent: Oct 23, 2007 3:04 PM
>To: Perl6 Internals <[EMAIL PROTECTED]>
>Subject: A thesis on Parrot/ECMA
>
>Hi,
>
>For the interested reader:
>the following is a link to a thesis on Parrot and ECMA scr
chromatic wrote:
now, the creation of Parrot::Coroutine becomes (r21929) :
.local pmc coro
.const .Sub coro_sub = "enumerate_tree"
coro_class = get_class 'Parrot::Coroutine'
coro = coro_class.'new'('initial_sub' => coro_sub)
So, how translate it in PMC ?
I think it's some
Hi,
For the interested reader:
the following is a link to a thesis on Parrot and ECMA script I found
recently.
Part of it is in English.
http://users.fulladsl.be/spb1622/pjs/scriptie.pdf
On Tuesday 23 October 2007 09:40:29 François PERRAD wrote:
> I've the following problem in languages/lua/pmc/luathread.pmc :
>
> when the creation of Parrot::Coroutine
> (runtime/parrot/library/Parrot/Coroutine.pir) was :
>
> .local pmc coro
> .const .Sub coro_sub = "enumerate_tree"
>
I've the following problem in languages/lua/pmc/luathread.pmc :
when the creation of Parrot::Coroutine
(runtime/parrot/library/Parrot/Coroutine.pir) was :
.local pmc coro
.const .Sub coro_sub = "enumerate_tree"
coro = new 'Parrot::Coroutine', coro_sub
in luathread.pmc, I wrote (t
Allison Randal schrieb:
As a general rule of thumb, if you find a failure but don't have the
time/expertise to debug it or classify it as TODO or BUG or "new
underdocumented feature", but do have enough time to create a failing
test for the problem (always nice), submit a ticket explaining the
26 matches
Mail list logo
