Re: [perl #49972] Error message for misspelled sub name in PIR code is confusing

2008-05-06 Thread chromatic
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 > http://groups.google.com/group/perl.perl6.internals/msg/7343

Re: [perl #49972] Error message for misspelled sub name in PIR code is confusing

2008-01-21 Thread Klaas-Jan Stol
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

Re: [perl #49972] Error message for misspelled sub name in PIR code is confusing

2008-01-19 Thread Geoffrey Broadwell
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 parti

Re: [perl #49972] Error message for misspelled sub name in PIR code is confusing

2008-01-19 Thread Patrick R. Michaud
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 > >