Gregor N. Purdy [EMAIL PROTECTED] wrote:
..., but I didn't want to make
2 * N new .c files to get paranoid versions of the N core .c
files now.
One safe core, built separately with its own Ops files ought to be
enough, IMHO.
I thought about prederef a bit right before submitting this, and
Jeff Clites [EMAIL PROTECTED] wrote:
I'd imagine this indicates a behavior change in imcc at some point.
Or no one ran these tests since assemble.pl was used :)
It's easy enough to add the LFs, but it might be better to not require
the final line end character.
The parsing pod says that
# New Ticket Created by Michael Scott
# Please include the string: [perl #24115]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=24115
I've made the changes necessary to bring strings.pod up-to-date.
Here's the
Michael Scott [EMAIL PROTECTED] wrote:
I've made the changes necessary to bring strings.pod up-to-date.
Applied, thanks.
leo
Ok, I'm back to argument passing. I'm starting a new thread because
I'm lazy and I have to scroll back too far in my mailer to see the old
arg passing thread. :-) And yes, most of this message should also be
on -languages.
Could somebody tell me where I go wrong:
If you have a prototype
sub f
Dan Sugalski [EMAIL PROTECTED] wrote:
Fair enough, but I don't want to ship the PCRE sources, nor require
them for parrot to build, so there's something of a problem there,
unfortunately.
So I'll make a lib ouf of it.
Where do you prefer it to go:
* runtime/parrot/lib/
* library/
leo
Steve Fink writes:
Ok, I'm back to argument passing. I'm starting a new thread because
I'm lazy and I have to scroll back too far in my mailer to see the old
arg passing thread. :-) And yes, most of this message should also be
on -languages.
Which it now is. Although, there are some
On Oct-05, Luke Palmer wrote:
Steve Fink writes:
Ok, I'm back to argument passing. I'm starting a new thread because
I'm lazy and I have to scroll back too far in my mailer to see the old
arg passing thread. :-) And yes, most of this message should also be
on -languages.
Which it now