It seems that PIR uses only one name space of identifiers.
$ cat const.pir
.const int cst = 42
.sub 'cst'
print cst
.end
$ parrot const.pir
error:imcc:undefined identifier 'cst'
in file 'const.pir' line 5
$ cat label.pir
.const int L1 = 42
.sub 'main'
print L1
goto L1
Klaas-Jan Stol wrote:
This must make the following syntax rule illegal:
target = null
because if null is declared as a .local, you can't know whether you want
to nullify target, or want to set target's value to that of the .local
variable null.
I take it this is no problem; just stick to
On Tue, Sep 2, 2008 at 12:43 PM, Allison Randal [EMAIL PROTECTED] wrote:
Klaas-Jan Stol wrote:
This must make the following syntax rule illegal:
target = null
because if null is declared as a .local, you can't know whether you want
to nullify target, or want to set target's value to
Klaas-Jan Stol wrote:
So, preferably, the special words in PIR will be allowed as identifiers
('if','unless', 'null') and PIR will DWIM. What about the type identifiers:
int, num, pmc, string; should these be allowed as identifiers? The currently
special PIR words such as if, unless, null are
On Tue, Sep 2, 2008 at 2:28 PM, Allison Randal [EMAIL PROTECTED] wrote:
Klaas-Jan Stol wrote:
So, preferably, the special words in PIR will be allowed as identifiers
('if','unless', 'null') and PIR will DWIM. What about the type
identifiers:
int, num, pmc, string; should these be allowed
# New Ticket Created by Stephane Payrard
# Please include the string: [perl #58488]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=58488
One can crash calling rakudo on a file containing
eval 'class A { has $.a};
# New Ticket Created by Stephen Weeks
# Please include the string: [perl #58506]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=58506
The attached pir file tries to call a sub set :outer() another sub
without calling
On Wed Aug 27 22:49:37 2008, cotto wrote:
Most of these test wouldn't throw an exception anyway, since assigning
to a positive out-of-bounds element simply resizes the array. (This
excludes nonsensically large positive indicies, which should probably
tested for.) I added exception handling
Attached is a new patch for the cygwin070patches. This is against svn,
so it replaces the patches _6 and _7.
Fixed some logical flaw and enhanced the Makefiles.
Renamed TMP to HLLNAME.
--
Reini Urban
http://phpwiki.org/ http://murbreak.at/
cygwin070patches_8.patch.gz
Description: GNU Zip
I don't get a segfault when running the test case without the 'end'
opcode. Can anyone else confirm if this still segfaults?
cet.pir
Description: Binary data
From: Stephen Weeks (via RT) [EMAIL PROTECTED]
Date: Tue, 02 Sep 2008 01:21:49 -0700
# New Ticket Created by Stephen Weeks
# Please include the string: [perl #58506]
# in the subject line of all future correspondence about this issue.
# URL:
From: Bob Rogers [EMAIL PROTECTED]
Date: Tue, 2 Sep 2008 21:55:54 -0400
. . . I suspect this faked call is what's causing the too few
arguments error (though none of my naive attempts to fix it worked).
If this case is not covered by the test suite (I'm running an
experiment now
12 matches
Mail list logo
