Re: g_malloc overhead

[Owen Taylor <otaylor redhat com>]

On Mon, 2009-01-26 at 18:30 +0100, Martín Vales wrote:
> Colin Walters escribió:
> > On Mon, Jan 26, 2009 at 9:12 AM, Behdad Esfahbod <behdad behdad org> wrote:
> >   
> >> Lets just say that
> >> UTF-16 is at best implementation details of Firefox.
> >>     
> >
> > Well, JavaScript is notably UTF-16.  Given that the Web, Java and .NET
> > (i.e. all the most important platforms) are all UTF-16 it's likely to
> > be with us for quite a while, so it's important to understand.
> >   
> Yes i only wanted say that. For example i work in c# and i would like 
> create glib libraries and use it in .net, but the "char" in mono/.NET is 
> utf16  and therefore i have there the same overhead.
> 
> The solution are 2:
> 
> 1.- conversion using glib ():
> http://library.gnome.org/devel/glib/2.19/glib-Unicode-Manipulation.html#gunichar2
> .-2. automatic NET conversion in the p/invoke side.
> 
> The 2 solutions have the same overhead.
> 
> > But yeah, there's no way POSIX/GNOME etc. could switch even if it made
> > sense to do so (which it clearly doesn't).
> >   
> Yes, i only talked about the overhead with utf8 outside of glib, only that.
> Perhaps the only solution is add more suport to utf16 in glib with more 
> methods.
> 

There's zero point in talking about a "solution" until you have profile
data indicating that there is a problem.

- Owen