From:	"Damian Yerrick" <die DOT spammers AT pineight DOT 8m DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Annoying: const char * in Allegro
Date:	Sat, 4 Sep 1999 14:42:18 -0500
Organization:	Rose-Hulman Institute of Technology
Lines:	10
Message-ID:	<7qrsqb$s9e$1@solomon.cs.rose-hulman.edu>
NNTP-Posting-Host:	yerricde.laptop.rose-hulman.edu
X-Trace:	solomon.cs.rose-hulman.edu 936474251 28974 137.112.205.146 (4 Sep 1999 19:44:11 GMT)
X-Complaints-To:	news AT cs DOT rose-hulman DOT edu
NNTP-Posting-Date:	4 Sep 1999 19:44:11 GMT
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE:	Produced By Microsoft MimeOLE V5.00.2314.1300
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

All of Allegro's string-handling (textout(), textprintf(), files, etc.)
functions take a char * instead of a const char *. Anyone know why? Do they
change the strings in some subtle way? As it stands now, I have to do
dangerous casts to get my const char * parameters to work without errors or
warnings.

Damian Yerrick

- Raw text -