From: Schuster <Schuster AT eev DOT e-technik DOT uni-erlangen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: allegro 2.2 's textout function
Date: Thu, 27 Feb 1997 08:37:03 -0800
Organization: Lehrstuhl fuer Elektrische Energieversorgung
Message-ID: <3315B82F.4A6F@eev.e-technik.uni-erlangen.de>
References: <199702251244 DOT NAA06888 AT gil DOT physik DOT rwth-aachen DOT de>
	 <5ev21b$iav AT news DOT ox DOT ac DOT uk> <33147146 DOT 6CAB AT eev DOT e-technik DOT uni-erlangen DOT de> <x3E$qCAytJFzEwpN AT talula DOT demon DOT co DOT uk>
NNTP-Posting-Host: eev6.e-technik.uni-erlangen.de
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 23
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Shawn Hargreaves wrote:
> I changed this while I was extending the font routines to support
> extended character sets, because the unsigned char type makes more sense
> for storing characters above 127. It never occured to me that this would
> break any code, but if it is a problem for people, it can easily be
> changed back. Opinions, anyone?

Thanks for all answers. 
I see the reason, and agree.
I think, I was to lazy to write (unsigned char*) before "HELLO" in

    textout(screen,font,(unsigned char*) "HELLO",20,10,1)

, as I didn't see a reason, why a textout-function should have a
stringargument which has to be converted when using "" - constants as 
"HELLO".

Michi
**********************************************
Michael Schuster
E-mail: Schuster AT eev DOT e-technik DOT uni-erlangen DOT de
Lehrstuhl fuer Elektrische Energieversorgung
http://www.eev.e-technik.uni-erlangen.de/