Applied as r13307.
Still needs some tweaking, e.g. fix the failing past.t, but good enough
for now.
leo
a chat about other possible API's which could be
added in future. Some e.g.
1. To throw Parrot exceptions instead of the String **error.
2. Possibly using Compiler PMC. (not sure on that yet)
Your suggestion is good and I will keep in mind.
These two functions are just a start for def
On Wednesday 12 July 2006 22:02, Vishal Soni via RT wrote:
> This patch also introduces a Parrot API for the calling programs to
> compile the code. Currently pugs uses immc_compile() call into IMCC.
> Ideally Pugs should not be communicating with IMCC but with Parrot. This
> new API will try to h
Hi,
I would like to throw a Parrot Exception from IMCC to the calling
program instead of terminating IMCC when a parse error occurs.
Are there some example in Parrot as to how to throw a Parrot exception
and how to catch it?
-Vishal
# New Ticket Created by Audrey Tang
# Please include the string: [perl #39715]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39715 >
Currently, if you use IMCC inside embedded parrot (eg. when compiling
via PGE), when a sy
Pete Lomax <[EMAIL PROTECTED]> wrote:
> Null PMC access in set_integer_native()
This (and a lot of others) currently doesn't throw a real_exception, so
you can't catch it.
> P0 = _eh()
That calls the exception handler directly as a sub.
> PS getline always returns 0, and getfile "(
Hi,
Just fishing for comments..
I have been experimenting with error handling, using
P9 = 1
to force the error:
Null PMC access in set_integer_native()
(others too, such as "Key not an integer!" or "Array index out of
bounds!").
I have found that:
newsub P0, .Exception
