On 9/15/06, Leopold Toetsch [EMAIL PROTECTED] wrote:
Am Freitag, 15. September 2006 01:42 schrieb Karl Forner:
But by looking in other tests and in the Parrot::Test, it seems that the
canonical way
of running a PIR script is through the example_output_is() function.
BUT this function does
Apparently they are the same. Merged as #14635
Alberto
Alberto Simões wrote:
Hi
When searching for globals on PIR parser (most of these globals are in
the top of imcc.y file) I found:
imcc.y:
SymReg *cur_namespace; /* ugly hack for mk_address */
imc.h:
typedef struct _imc_info_t {
Am Sonntag, 17. September 2006 15:16 schrieb Karl Forner:
I'd subclass Parrot::Test and create a function shootout_output_is(),
which
takes an extra commandline argument.
Hmmm but if I subclass Parrot::Test, I won't be able to reuse any code.
There are already Test classes: see
Hi everyone,
I just tried to build parrot (something I hadn't done in about a month
and a half) and it failed to build due to gmp_version being undeclared
in src/pmc/bigint.pmc (not suprising since I don't have GMP installed).
Attached is a patch that fixes the problem for me. Using the
Hi, fixed
svnbotl r14636 | leo++ | trunk:
svnbotl : fix BigInt.version if gmp isnt installed
David Romano wrote:
Hi everyone,
I just tried to build parrot (something I hadn't done in about a month
and a half) and it failed to build due to gmp_version being undeclared
in
Hi everyone,
When building parrot on my iBook, two tests that depend on PCRE failed
because I don't have PCRE installed and the code that determines if
PCRE is installed is faulty. Parrot::Test::run_command returns [SIGNAL
$exit_code] if the exit code of the commands are not divisible by 256,
or
# New Ticket Created by Ron Blaschke
# Please include the string: [perl #40347]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=40347
This is because Parrot::Revision scans .svn/entries directly, but the
Subversion
The attached patch consolidates most of the existing stack-unwinding
code into Continuation:invoke; previously, RetContinuation:invoke and
find_exception_handler also did stack-unwinding, and none of the three
did it quite the same way.
Here are the effects:
1. Improved code sharing, a
