Re: [icu-support] bug in ucnv_safeClone?

[Markus S. <mar...@gm...>]

You should use U_CNV_SAFECLONE_BUFFERSIZE as an initial buffer size.
It should be large enough.

ucnv_safeClone() does allow you to start with a size of 0 (see the API
documentation) - it just requires you to provide a pointer to the size
variable (which is an in/out parameter).

The documentation does say that if the pointed-to size is 0, it just
tells you the size. I guess it could be more explicit that in this
case it won't allocate anything.

I submitted two Jitterbugs on your behalf - an RFE (4492) for
accepting pBufferSize=3D=3DNULL and a docs bug (4493) to clarify the
*pBufferSize=3D=3D0 behavior.

Best regards,
markus
On 4/6/05, Adam Skwersky <ask...@us...> wrote:
>  I think I may have found a bug in ucnv_safeClone?=20
>=20
> You cannot pass a NULL value for the buffer size. ...