Re: File name encoding and GTK ABI compatibility on Win32

[Mike Hearn <mike navi cx>]

On Sun, 05 Dec 2004 19:52:55 +0000, Tor Lillqvist wrote:
> To avoid this, for all GLib functions that manipulate file names that
> have existed prior to 2.6, preprocessor #defines have been added to
> the corresponding headers that suffix the function names with _utf8
> (on Win32 only). For instance a call to g_dir_read_name() actually
> gets compiled as a call to g_dir_read_name_utf8(), etc. The
> corresponding GLib source files then also define backward
> compatibility versions of the functions with the old name, that behave
> like before.

If you are going to do this, please make it optionally enabled (tied to
the win32 UNICODE macro, perhaps?). Please don't just magically make
programs compiled against the glib 2.6 headers silently depend on 2.6 only
symbols. This is unintuitive and isn't the Windows methodology anyway.

thanks  -mike