Subject: [clisp-list] Re: clear-input not working from dos box?

From: "Hoehle, Joerg-Cyril" <[email-masked]>
Date: Mon Nov 11 05:39:02 2002

Kaz Kylheku wrote:

> then type (on one line)
>  2 3 4 5
>This is probably because CLISP is reading your terminal input in
>character-at-a-time mode. So the read of 3 completes as soon as the
>space character is read in, and no additional characters are buffered
>from the operating system. No characters buffered means that there is
>nothing to discard. This is how CLISP behaves on Unix.

Strange. This differs from how - unverified - CLISP behaves on AmigaOS, where, even in character a t a t i m e mode, the input device (and associate processes) will know that 4 and 5 have already been typed (the keystrokes made it to the OS, after all!), and an application can query this fact, so CLISP will skip past them.

Is readline active in Don's windows CLISP?

Does type ahead cause trouble when CLISP enters a debugger loop or does discarding input work fine there? That's the typical use-case for CLEAR-INPUT.

BTW, Kaz, thanks for your informative posts on various subjects, e.g. FFI.

Regards,
	Jorg Hohle.