opengroup:
http://www.opengroup.org/onlinepubs/007904975/functions/iconv.html
size_t iconv(iconv_t cd, char **restrict inbuf,
size_t *restrict inbytesleft, char **restrict outbuf,
size_t *restrict outbytesleft);
HP-UX:
http://docs.hp.com/hpux/onlinedocs/B2355-90683/00/02/280-con.html
size_t iconv(
iconv_t cd,
const char **inbuf,
size_t *inbytesleft,
char **outbuf,
size_t *outbytesleft
);
AIX:
http://publib16.boulder.ibm.com/doc_link/en_US/a_doc_lib/libs/basetrf1/iconv.htm
size_t iconv (CD, InBuf, InBytesLeft, OutBuf, OutBytesLeft)
iconv_t CD;
char **OutBuf, **InBuf;
size_t *OutBytesLeft, *InBytesLeft;
Solaris:
http://docs.sun.com/db/doc/817-0677/6mgf9b64b?q=iconv&a=view
size_t iconv(iconv_t cd, const char **inbuf, size_t *inbytesleft, char
**outbuf, size_t *outbytesleft);
...
As there seems no authoritative specification for iconv(), I don't think
it's a good idea to *fix* the warnings with some quick tricks. Personally
I think the const'ified version should be correct..
Moriyoshi
Derick Rethans <[EMAIL PROTECTED]> wrote:
> On Sat, 6 Sep 2003, Moriyoshi Koizumi wrote:
>
> > You can safely ignore those warnings, which may be caused by differences
> > of the prototype between libiconv and glibc.
>
> I still think that it needs to be 'fixed', as this confuses users (and
> it just looks ugly :).
>
> Derick
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
