Bernhard Schmalhofer (via RT) wrote:
# New Ticket Created by Bernhard Schmalhofer
# Please include the string: [perl #45109]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=45109
In languages/lisp/system.pir
Bernhard Schmalhofer (via RT) wrote:
# New Ticket Created by Bernhard Schmalhofer
# Please include the string: [perl #45109]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=45109
In languages/lisp/system.pir
On 02/09/07, James E Keenan [EMAIL PROTECTED] wrote:
On Sep 1, 2007, at 1:58 PM, Gabor Szabo wrote:
One thing though, I think it would be really good if at least the
exit code of
the script would be something different from 0 when any of the
steps failed.
That will be very
On 01/09/07, Ron Blaschke [EMAIL PROTECTED] wrote:
Paul Cochrane wrote:
I've had a chance to look at this and the implementation looks quite
good to me.
There's one thing that still bothers me. The snipped output is:
Event alias: aliasing (ins)-next with ins2
Also see events:
Andrew Dougherty wrote:
Meanwhile, this patch should clean up some bit rot and document it all a
little better.
Thanks, applied.
Allison
Ron Blaschke via RT schrieb:
In all three sections a value is loaded into a register and then set as
an attribute on an object.
In the first hunk only the used register is changed from 0x12 to 0x13.
In the second hunks it's register 0x11 to 0x12.
With hunk three it's getting interesting
Bernhard Schmalhofer wrote:
Ron Blaschke via RT schrieb:
In all three sections a value is loaded into a register and then set as
an attribute on an object.
In the first hunk only the used register is changed from 0x12 to 0x13.
In the second hunks it's register 0x11 to 0x12.
With hunk three
not surprisingly, it looks like some symbols in libparrot conflict with
exported symbols from other libraries. i ran into this when testing
mod_parrot on an apache server with PHP 5 configured:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1077226080 (LWP 9187)]
On Sat, 1 Sep 2007, Gabor Szabo wrote:
It has biten me so let's make sure invalid --gc options are not allowed.
But what if I want to work on --gc=libc? How can I override this?
--
Andy Dougherty [EMAIL PROTECTED]
