From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,81455da56a5b63c4 X-Google-Attributes: gid103376,public From: kilgallen@eisner.decus.org (Larry Kilgallen) Subject: Re: Character input (no echo).... Date: 1997/03/05 Message-ID: <1997Mar5.144903.1@eisner>#1/1 X-Deja-AN: 223351386 X-Nntp-Posting-Host: eisner.decus.org References: <01bc298f$ce9896e0$f5093e9f@lsm8-pc.linkabit.titan.com> X-Nntp-Posting-User: KILGALLEN X-Trace: 857591349/2629 Organization: LJK Software Newsgroups: comp.lang.ada Date: 1997-03-05T00:00:00+00:00 List-Id: In article <01bc298f$ce9896e0$f5093e9f@lsm8-pc.linkabit.titan.com>, "Marc Bejerano" writes: > How do I do this? I tried using a C import (remaps getch(stdin)...etc) but > it did not have the desired effect. FWIW I am running under Win95/NT and > would like this to be as transparent as possible so as not to be tied to > the platform. Isn't there a C library function that will let me read the > keyboard (including the decoding of functions keys) etc.? Independent of Ada, some operating systems will echo characters before a program call to read them, meaning you cannot be certain the character hasn't already been echoed by the time your program takes the action to avoid the echo. Portable solutions are thus unlikely, although a good try can be had by only hiring slow typists. Larry Kilgallen