Re: [perl #17035] [PATCH] chr support => strange behavior

2002-09-08 Thread Jerome Quelin
On Jeudi 5 Septembre 2002 17:08, Dan Sugalski wrote : > At 3:04 PM + 9/5/02, Leon Brocard (via RT) wrote: > >I realise that proper Unicode support is coming, but it may be a while > >to get here. We currently have ord() and it makes sense to have a > >chr() as well, so that's what my patch pro

Re: [perl #17035] [PATCH] chr support => strange behavior

2002-09-08 Thread Jerome Quelin
On Dimanche 8 Septembre 2002 11:28, Jerome Quelin wrote : > In fact, I tried to change S0, and whatever S0 value is (I tried with > several values: "<", ">", "A", "0", " "), I always get a 60 as its ordinal > value... I forgot to tell you: it doesn't work when I try to change S0 from the test se

Re: [perl #17035] [PATCH] chr support => strange behavior

2002-09-08 Thread Peter Gibbs
Jerome Quelinm wrote: > > In fact, I tried to change S0, and whatever S0 value is (I tried with > > several values: "<", ">", "A", "0", " "), I always get a 60 as its ordinal > > value... > > I forgot to tell you: it doesn't work when I try to change S0 from the test > set. But when I try to put a

Re: [perl #17035] [PATCH] chr support => strange behavior

2002-09-08 Thread Jerome Quelin
On Dimanche 8 Septembre 2002 11:50, Peter Gibbs wrote : > This looks like a COW bug. Try the attached patch (untested). In fact, here's the minimal test case: $ cat p.pasm <" print I10 print "<\n" end EOF $ perl ../../assemble.pl p.pasm >P.pbc $ ../../parrot P.pbc >v< >97<

[perl #17071] [PATCH] string_index COW bug (and test)

2002-09-08 Thread via RT
# New Ticket Created by Peter Gibbs # Please include the string: [perl #17071] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt2/Ticket/Display.html?id=17071 > Attached patch fixes a problem with ord reported by Jerome Quelin. It also includes a te

[perl #17072] warnings while compiling parrot

2002-09-08 Thread via RT
# New Ticket Created by Jerome Quelin # Please include the string: [perl #17072] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt2/Ticket/Display.html?id=17072 > I just rsync-ed my parrot. $ perl Configure.pl [...] $ make [...] string.c: In functi

Parrot_interp, DOD and?

2002-09-08 Thread Leopold Toetsch
if I knew, what exactly to ask, it where easier. I'm implementing a parrot interpreter in immc. I seem to have memory corruptions or unreproducible errors. E.g. moving the stacktop variable only slightly gives different test results, as well as results on a second machine differ. Blocking

vi modelines for the boilerplate (was Re: [PATCH] COW for ithreads (was Re: what copies scalars in ithreads?))

2002-09-08 Thread Nicholas Clark
from perl5-porters: On Sun, Sep 08, 2002 at 09:47:24PM +0200, Rafael Garcia-Suarez wrote: > Nicholas Clark wrote: > > Are we going to assimilate what parrot is doing in all its C files - > > > > /* > > * Local variables: > > * c-indentation-style: bsd > > * c-basic-offset: 4 > > * indent-ta

Re: [perl #17039] [PATCH] intarray aka integer dequeue PMC

2002-09-08 Thread Steve Fink
On Thu, Sep 05, 2002 at 07:46:38PM -0400, John Porter wrote: > Steve Fink wrote: > > Here is the new PMC I keep babbling about. Before I commit it, any > > comments? Like, does anybody think this should be named differently? > > It's really a dequeue (double-ended queue), ... > > I for one think

Re: [perl #17035] [PATCH] chr support => strange behavior

2002-09-08 Thread Steve Fink
On Sun, Sep 08, 2002 at 11:50:10AM +0200, Peter Gibbs wrote: > Jerome Quelinm wrote: > > > In fact, I tried to change S0, and whatever S0 value is (I tried with > > > several values: "<", ">", "A", "0", " "), I always get a 60 as its > ordinal > > > value... > > > > I forgot to tell you: it doesn'

Re: [perl #17071] [PATCH] string_index COW bug (and test)

2002-09-08 Thread Steve Fink
On Sun, Sep 08, 2002 at 10:35:16AM +, Peter Gibbs wrote: > > Attached patch fixes a problem with ord reported by Jerome Quelin. > It also includes a test case in string.t. Oops, I thought this patch was for something else. Oh well, I've applied the fix already, with an equivalent test case, s

Re: [perl #17067] [PATCH] Buffers shouldn't remain free after being allocated

2002-09-08 Thread Steve Fink
On Sat, Sep 07, 2002 at 09:17:38AM +, Peter Gibbs wrote: > > Mike's changes to integrate the external and selfpoolptr flags > have resulted in the on_free_list flag remaining set when a > buffer header is reallocated. > > This breaks life, so I have had to fix it to be able to compare > tim