On Wed, 18 Dec 1996, Glenn Adams wrote:
> I couldn't agree with you more. I'm deeply mired in attempting to build
> a cross-platform product (win,mac,8 unix flavors,qnx,os/9,psos,...) written
> primarily in C and consistently use UCS-2 character data throughout. The
> most significant problems I face are:
> 1. lack of compiler support for wchar_t (and wide string literals in
> particular); or if a compiler supports wchar_t, then lack of control
> over whether 16-bits or 32-bits are used.
I once published a workaround for this. Please see
> 2. lack of standard runtime support for wchar_t signatures; i.e., there
> needs to be a standard set of wcs entry points for string.h, ctype.h,
> stdlib.h, stdio.h, etc.
Gets easier with overloading in C++. For some cases, i.e. ctype.h,
the problem is that the semantics have to be extended (and agreed upon)
before getting the libraries.
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:33 EDT