Date: Sun, 14 Jun 1998 14:13:18 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Gili <sl AT psycode DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: ScreenGetChar -- VERY DANGEROUS!
In-Reply-To: <bWLoegW7sFse-pn2-2so6hnnhW8Uj@portF68.Generation.NET>
Message-ID: <Pine.SUN.3.91.980614141252.6294b-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On 14 Jun 1998, Gili wrote:

> The problem was that I had " BYTE* character" which I 
> was casting into (int*) and using in ScreenGetChar().. Little did I 
> know that ScreenGetChar() is very sensative about this issue and it 
> lead to seemingly random SIGSEGV errors poping up everywhere.. Please 
> add some sort of warning about this in the DOCs. Thank you,

I don't really understand what did your code try to do.  Did you try
to pass pointers to a char as the first and the second arguments of
the function?  If so, this is basic C: any program that does this
risks a crash.  I don't think libc.info can explain all of the
pitfalls of using incorrect C code.

Please explain in more detail what did you try to do, including a
short code snippet.