Re[8]: non unicode build

[Arseny S. <am...@ic...>]

Hello Sam,

Saturday, October 27, 2001, 3:48:54 AM, you wrote:

>> (but still needs a Windows 95/98 patching).
Sam> I am not sure this is a top priority.
Sam> do you think many people still use w95/98?
I don't see many people in clisp-list and c.l.l
who using any of the microsoft systems at all (But many
newbies do). And you are right, that console stuff
should consume less traffic. But it makes possible
to create programs of almost maximum portability,
lets to create eternal programs depending on 14
interface functions working on almost any platform !

There are two problems with w95/98(shortly): console
reusing (CreateConsoleScreenBuffer on w95/98 seems
returning something which should not be closed) and
localized keyboard codes in with-keyboard
mode. First can be solved quite simple in stream.d,
second requires to change a number of files including
keyboard.lisp (with-keyboard) while it not very complex too.
So let shedule last to when somebody will need it.
As for first, I think it will be better to patch it in
advance because now it much like a bug. Patch inside.

BTW, there is another way to handle Ctrl-C in win32,
it can be read as regular key (no suffer with
threads).

I remake makefile.msvc5 for UNICODE and !UNICODE as
you suggested, it was required to load FreeBSD
(makemake is a shell script).

-- 
Best regards,
 Arseny