From: Shawn Hargreaves <Shawn AT talula DOT demon DOT co DOT uk>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: allegro 2.2 's textout function
Date: Wed, 26 Feb 1997 20:22:10 +0000
Organization: None
Distribution: world
Message-ID: <x3E$qCAytJFzEwpN@talula.demon.co.uk>
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>
NNTP-Posting-Host: talula.demon.co.uk
MIME-Version: 1.0
Lines: 16
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Schuster writes:
>I'm writting on a c++ program with Allegro. I switched to alleg22 beta
>and now get a lot of warnings, cause the textout-function claims that
>the char*  argument should be "unsigned char* ". Why this change?
>Is there any way to get rid of it or change it to the old way?

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?

/*
 *  Shawn Hargreaves - shawn AT talula DOT demon DOT co DOT uk - http://www.talula.demon.co.uk/
 *  Beauty is a French phonetic corruption of a short cloth neck ornament.
 */