Re: [PATCH] tabs->spaces fix

Sorry. It's easier to c+p into Pine than it is to upload+attach. I have a feeling a few other patches I've submitted might be screwed up as well. If this happens for anyone, please let me know. Mike Lambert Josh Wilmes wrote: > Date: Mon, 25 Mar 2002 23:22:34 -0500 > From: Josh Wilmes <[EMAIL P

[PATCH] Stack bugfix

As requested, I wrote a nasty little recursive program to test strings, memory and call stacks. Immediately bad stuff happened when the stack frames outgrew a single chunk and a new one was allocated. When the frame stack reached FRAMES_PER_CHUNK, the new chunk gets allocated, etc, etc. and bad st

Status of keyed support?

What's the current status of support for keyed ops? I'm tempted to slap together at least partial support for some keyed operations (they'd make some of my test code simpler, at the very least), but I'd rather not work on out of date code. And I don't completely understand what needs to be done.

Re: [PATCH] tabs->spaces fix

Mike, that doesn't want to apply for me- i suspect that the patch got garbled in the mail. Can you MIME-attach or uuencode it? --Josh At 23:17 on 03/25/2002 EST, Michel J Lambert <[EMAIL PROTECTED]> wrote: > Below is a fix for the use of tabs in test_main.c and resources.c. > > Mike Lamber

[PATCH] tabs->spaces fix

Below is a fix for the use of tabs in test_main.c and resources.c. Mike Lambert Index: resources.c === RCS file: /cvs/public/parrot/resources.c,v retrieving revision 1.33 diff -r1.33 resources.c 23,24c23,24 <

Re: Unicode thoughts...

Jeff wrote: > > Hong Zhang wrote: > > > > I think it will be relative easy to deal with different compiler > > and different operating system. However, ICU does contain some > > C++ code. It will make life much harder, since current Parrot > > only assume ANSI C (even a subset of it). > > > > Hon

Re: Unicode thoughts...

Hong Zhang wrote: > > I think it will be relative easy to deal with different compiler > and different operating system. However, ICU does contain some > C++ code. It will make life much harder, since current Parrot > only assume ANSI C (even a subset of it). > > Hong > > > This is rather conce

RE: Unicode thoughts...

I think it will be relative easy to deal with different compiler and different operating system. However, ICU does contain some C++ code. It will make life much harder, since current Parrot only assume ANSI C (even a subset of it). Hong > This is rather concerning to me. As I understand it, on

Re: Unicode thoughts...

This is rather concerning to me. As I understand it, one of the goals for parrot was to be able to have a usable subset of it which is totally platform-neutral (pure ANSI C). If we start to depend too much on another library which may not share that goal, we could have trouble with the par

RE: Unicode thoughts...

> We also need to make sure ICU will work everywhere. And I do mean > *everywhere*. Will it work on VMS? Palm OS? Crays? Nope, nope, and nope. >From their site - Operating systemCompilerTesting frequency Windows 98/NT/2000 Microsoft Visual C++ 6.0Reference pl

RE: Unicode thoughts...

Jeff: # This will likely open yet another can of worms, but Unicode has been # delayed for too long, I think. It's time to add the Unicode libraries # (In our case, the ICU libraries at , # which Larry has now blessed) to Parrot. string.c already has # (admittedly

Re: Old Warnock's Dilemma for 'make quicktest'

Michel J Lambert: > +=item B I noticed that "make testj" and "make testp" exist too. -- DEC diagnostics would run on a dead whale. -- Mel Ferentz

Re: Old Warnock's Dilemma for 'make quicktest'

>This satisfactory? (I didn't mention it in the README because that's >supposed to be simpler instructions sans caveats, imo) Looks good to me. Thanks, Applied! -R

Minor GC Patch, and Some Questions

Below is a cleanup patch for a comment or two, some flags missing, that I did while reading through it all in an attempt to figure it all out. I was impressed with how straightforward all the code was, but there were a few things that confused me. If you answer these, I can provide documentation