On Fri Jan 18 21:41:00 2008, japhb wrote:
---
osname= linux
osvers= 2.6.22.10
arch= i486-linux-gnu-thread-multi
cc= cc
---
Flags:
category=core
severity=low
ack=no
---
The error message from parrot when there is a spelling mismatch
between
a function call and the
In r27351 I've added code to PCT to check for non-existent subs and
throw an exception at the point of the call. So, the problem is
solved for PCT-based languages, at least.
It still doesn't help with the case of non-existent sub names in PIR,
though, for which I recommend something along the
On Tuesday 06 May 2008 11:03:08 Patrick R. Michaud via RT wrote:
It still doesn't help with the case of non-existent sub names in PIR,
though, for which I recommend something along the lines of the patch
described by chromatic in
On Jan 20, 2008 1:34 AM, Geoffrey Broadwell [EMAIL PROTECTED] wrote:
On Sat, 2008-01-19 at 16:12 -0600, Patrick R. Michaud wrote:
On Fri, Jan 18, 2008 at 09:41:01PM -0800, Geoffrey Broadwell wrote:
Null PMC access in invoke(); misspelled sub name in function call?
I fear this error
# New Ticket Created by Geoffrey Broadwell
# Please include the string: [perl #49972]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=49972
---
osname= linux
osvers= 2.6.22.10
arch= i486-linux-gnu-thread-multi
cc=
On Fri, Jan 18, 2008 at 09:41:01PM -0800, Geoffrey Broadwell wrote:
The error message from parrot when there is a spelling mismatch between
a function call and the function's actual declaration is accurate but
confusing:
*
$ cat foob.pir
.sub main :main
foo()
.end
.sub foob
On Sat, 2008-01-19 at 16:12 -0600, Patrick R. Michaud wrote:
On Fri, Jan 18, 2008 at 09:41:01PM -0800, Geoffrey Broadwell wrote:
Null PMC access in invoke(); misspelled sub name in function call?
I fear this error message may actually send a beginner down a false
trail. This particular
