It's a good timing to make my first post to this mailing list. On Thursday, May 30, 2002, at 09:04 PM, Bryan C. Warnock wrote: > On Tue, 2002-05-28 at 17:42, George Rhoten wrote: > >> It is true that parts of ICU uses C++. Some parts of ICU are written >> in C++ >> with a C wrapper. Some other parts are written in C with a C++ >> wrapper. It >> depends on the API being used. Most of the functionality in the common >> library is written in C, and most of our i18n library uses C++. You >> can see >> some of the C/C++ dependencies here >> http://oss.software.ibm.com/icu/userguide/design.html under API >> dependencies. >> >> The vast majority of people that we encounter do have a C++ compiler, >> and > > What exactly does that mean? When I first read this, I thought, "Well, > duh! If C++ is a requirement, then anyone wanting to interact with ICU > will have a C++ compiler. If they didn't have one, they wouldn't use > it." > > Or do you mean that ICU simply hasn't been approached (often) to provide > a C-only implementation?
Encode, the standard encoding engine for Perl 5.8 does not use ICU directly though it uses UCM. Chances are I'll port Encode to Perl6. Whether I'll use ICU or not I am not sure. Dan the Encode Maintainer
