That's a real PITA. How exactly are we supposed to handle platforms
this? Linux is getting warnings right now, which I dislike.
I am developing on Linux (RedHat 7) and was getting warnings with
the old code. I don't know why you are getting warnings from the
explicit cast. Are you using an
That's a real PITA. How exactly are we supposed to handle platforms
this? Linux is getting warnings right now, which I dislike.
I am developing on Linux (RedHat 7) and was getting warnings with
the old code. I don't know why you are getting warnings from the
explicit cast. Are you
Roy T. Fielding [EMAIL PROTECTED] 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
[EMAIL PROTECTED] wrote:
fielding01/01/28 03:33:55
Modified:i18n/unix xlate.c
include apr_xlate.h
Log:
Revert last change and solve warning by explicit cast. The need would
have been obvious if dependencies were in the Makefile.
Revision Changes
Eh? Why are you casting away the const???
Because, as noted in the earlier commit, the iconv function
does not have a const parameter, and the only reason this
variable is being used is for passing that parameter.
Blame it on whoever created the original iconv prototype
for the
size_t iconv(iconv_t cd, const char **inbuf, size_t *inbytesleft,
char **outbuf, size_t *outbytesleft);
That shows that SUSv2 is a descendant of XPG4 where this
specific iconv interface (with const) originated.
However, draft 5 of SUSv3 contains this
Btw, here is the reasoning for the change:
http://www.opengroup.org/sophocles/show_mail.tpl?source=Llistname=austin-group-lid=270
That's a real PITA. How exactly are we supposed to handle platforms
this? Linux is getting warnings right now, which I dislike.
Why is it a PITA?
