# New Ticket Created by Bob Rogers
# Please include the string: [perl #38239]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=38239 >
examples/pir/io.pir leaves the "tmp_example_io.tmp" in the cwd, even
when run as the f
hi,
I have 2 questions wrt PIR parameter notation and usage.
I'm not quite sure how I should specifiy the flags when using
get_params, instead of the .param notation.
according to PDD03, flag "3" is for specifiying slurpy parameters.
Should I type:
get_params "(3)", $P0
to say $P0 is a s
From: Klaas-Jan Stol <[EMAIL PROTECTED]>
Date: Sun, 15 Jan 2006 18:16:00 +0100
hi,
I have 2 questions wrt PIR parameter notation and usage.
I'm not quite sure how I should specifiy the flags when using
get_params, instead of the .param notation.
according to PDD03, flag "3"
On Jan 14, 2006, at 17:30, Joshua Isom wrote:
src/ops/experimental.ops:226: error: unable to find a register to
spill
I've now disabled register assignment for gcc like ...
register opcode_t *cur_opcode asm ("esi") = cur_op;
... totally. It works for some gcc 3.x versions though and can
On Jan 15, 2006, at 18:16, Klaas-Jan Stol wrote:
get_params "(3)", $P0
That's already answered, it's bit 3, 1 << 3, or 0b1000, or 0x8.
.param $P0
E.g.:
.param pmc p0:optional
.param int has_p0:opt_flag
or
.param pmc args :slurpy
or even:
(result :slurp
On Jan 14, 2006, at 21:28, Bob Rogers wrote:
I had thought this field was being used, but it turns out to be
irrelevant. I offer this patch so that no one else is fooled (and
because I had to test it anyway to prove that this is the case).
Thanks, applied - r11199
leo
# New Ticket Created by Leopold Toetsch
# Please include the string: [perl #38242]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=38242 >
On Jan 14, 2006, at 21:28, Bob Rogers wrote:
>I had thought this field was bei
* iff global lookup exceptions are off, a Null PMC is returned instead
of
Undef on lookup failure
This is necessary as a global .Undef with that global name could still
exist, but the difference WRT non-existing global isn't even testable
with 'defined'. Now ...
g = global 'foo'
if nul
I'm glad to report the soon-to-be-released Pugs 6.2.11 now targets
Parrot with the new calling convention and lexical pad syntax.
However, the explicit demand on a "newclosure" runtime call makes
package-scoped subroutines awkward to generate and use -- please see
this journal entry for details:
Dear Michael and Perl QA colleagues,
Wes Barris was trying to install one of my modules and encountered a
dependency problem when Test-Simple-0.62 failed to make on his system.
I was able to get some additional details, but I'm not sure what advice
to offer him. The problem appears to be in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm almost sure this had been covered before, but I failed to find a
reference in either the archives or in synopses, so here goes again:
sub f ($x) {
sub g ($y) { $x + $y }; g($x);
}
f(10); # 20?
Currently in Pugs, &g is built at
Per step parameter support implimented in r11203.
-J
--
12 matches
Mail list logo
