Re: Unicode thoughts...

Dan Sugalski wrote: > > At 10:07 AM -0500 3/30/02, Josh Wilmes wrote: > >Someone said that ICU requires a C++ compiler. That's concerning to me, > >as is the issue of how we bootstrap our build process. We were planning > >on a platform-neutral miniparrot, and IMHO that can't include ICU (as i'

Re: Unicode thoughts...

At 10:07 AM -0500 3/30/02, Josh Wilmes wrote: >Someone said that ICU requires a C++ compiler. That's concerning to me, >as is the issue of how we bootstrap our build process. We were planning >on a platform-neutral miniparrot, and IMHO that can't include ICU (as i'm >sure it's not going to be wr

Re: Unicode thoughts...

Someone said that ICU requires a C++ compiler. That's concerning to me, as is the issue of how we bootstrap our build process. We were planning on a platform-neutral miniparrot, and IMHO that can't include ICU (as i'm sure it's not going to be written in pure ansi C) --Josh At 8:45 on 03/3

RE: Unicode thoughts...

At 4:32 PM -0800 3/25/02, Brent Dax wrote: >I *really* strongly suggest we include ICU in the distribution. I >recently had to turn off mod_ssl in the Apache 2 distro because I >couldn't get OpenSSL downloaded and configured. FWIW, ICU in the distribution is a given if we use it. Parrot will re

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

Unicode thoughts...

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 unavoidable, du