Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Sender: trawick@bellsouth.net
To: dev@apr.apache.org
Subject: Re: cvs commit: apr/include apr_xlate.h
References: <Pine.LNX.4.30.0101281808250.417-100000@rossini.schumann.cx>
	<Pine.LNX.4.21.0101280926420.28992-100000@koj>
	<20010128174904.A803@waka.ebuilt.net>
From: Jeff Trawick <trawickj@bellsouth.net>
Date: 29 Jan 2001 08:08:27 -0500
In-Reply-To: "Roy T. Fielding"'s message of "Sun, 28 Jan 2001 17:49:04 -0500"
Message-ID: <m3d7d6wlo4.fsf@adsl-77-241-65.rdu.bellsouth.net>
Lines: 30
User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

"Roy T. Fielding" <fielding@ebuilt.com> writes:

>                                                 However, the code
> will work fine regardless of the warning, so it probably isn't
> worth the effort to support no warnings on anything but the latest
> gcc.

you mean the latest glibc

Previously, we had a warning on OS/390 and Tru64 (and I guess the level
of glibc which comes with RH 7) because they had no const, and a clean
compile everywhere else.  I left it alone since their iconv() did not
match the de facto standard and I didn't want to put in a cast that
people on normal systems would not understand.  I certainly didn't
want a cast which would cause warnings.  I had no qualms having the
warning on Tru64 and OS/390 (not that many people build it on these
platforms and it kept the code simpler).  Now, most users (I'm
guessing, but it seems like a safe guess) will see a warning, so
something needs to be done.

I'll look into using a different cast trick (or autoconf test) which
will avoid the warning on all platforms.  As long as there is a
reasonable comment in the code I suspect people will live it alone (do
you hear that Greg? :) )

Have fun...
-- 
Jeff Trawick | trawickj@bellsouth.net | PGP public key at web site:
       http://www.geocities.com/SiliconValley/Park/9289/
             Born in Roswell... married an alien...