You can use UNICOWS to run UNICODE build under Win9x.
<email@example.com> wrote in message
On 28 f?v, 12:47, David Wilkinson <no-re...@effisols.com> wrote:
I do not agree : 99% of the time, you should be using explicitely
either char, either wchar_t!! (but don't mix them of course).<
I don't agree with using percentages: I use CHAR WCHAR and TCHAR - the
last almost exclusively for the Windows/MFC interface (except for some
jobs involving symbol fonts where the ...W and ....A assume different
This whole idea of "Unicode build" or "Non-Unicode build" is a left-
over othe Win95/WinNT transition era, but nowadays,...
Currently I support Win98 with a non-Unicode build. (Which
nevertheless, with a view to the future, saves all text in its data files
as Unicode - hence explicit WCHARs) By my next release I'll probably be
able to forget it without offending too many people, and so my development
version is a Unicode build. It still has to read very old files with
CHAR strings included though - and always will do.
In other words, for those of us making our living from selling software to
home users, it is not a "left over" thing at all. One day it surely will
be, but right now we're on the cusp.
Author MOZART the music processor for Windows -
For discussion/support see