;.
According to that, NULL is defined in , , ,
, and .
--
-=( Ian Abbott @ MEV Ltd.E-mail: <[EMAIL PROTECTED]>)=-
-=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-
___
bug-gnulib mailing list
bug-gnulib@gnu.or
On 19/05/2005 11:18, Yoann Vandoorselaere wrote:
On Thu, 2005-05-19 at 10:47 +0100, Ian Abbott wrote:
On 18/05/2005 19:29, Yoann Vandoorselaere wrote:
It is not. The point was that the interface allow the user to specify a
callback for freeing the data, and thus the pointer to theses data
should
On 18/05/2005 19:29, Yoann Vandoorselaere wrote:
On Wed, 2005-05-18 at 16:16 +0100, Ian Abbott wrote:
On 17/05/2005 10:20, Yoann Vandoorselaere wrote:
However, I still consider this version of the patch to be a hack, when
the real bug here is that you should not use const since you permit the
user
show how the Hash_data_freer callback is called from
hash_insert, because I can't see it!
--
-=( Ian Abbott @ MEV Ltd.E-mail: <[EMAIL PROTECTED]>)=-
-=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-
___
bug-gnulib m
API on NT-based
Windows systems and the "8-bit character in current locale" API on
DOS-based Windows systems. It looks like Tor Lillqvist is mostly
responsible for this implementation.
--
-=( Ian Abbott @ MEV Ltd.E-mail: <[EMAIL PROTECTED]>)=-
es, of course.
Anyway, I was being a bit thick, because *all* bytes in a UTF-8 encoded
character > U+007F (i.e. all characters requiring more than one byte)
will be > 0x7F, so they won't contain 0x5C or 0x2F (or 0x3F:-).
--
-=( Ian Abbott @ MEV Ltd.E-mail: <[EMAIL PROTECTED
ASCII pathnames is inaccessible to GNU tools.
Microsoft recomments approach 1. GNOME has chosen approach 2. I would
favour answer 4.
What do you think?
Bruno
My gut instinct would be to use UTF-8 internally, but I'm not doing the
work! :-)
--
-=( Ian Abbott @ MEV Ltd.E-mail: &l
