> The meta-issue is that this code IS glib 2.0, so modifying our local
> copy without getting the changes into glib as well is the wrong thing,
> because in that case we might as well go back to libunicode.
I know. I am not advocating branching that part of glib. If
possible, we should try fixing their code and having the patches
committed to glib as well.
> The crashes and loops are caused by code that uses a macro (that does an
> array lookup and addition) instead of a function call. You could replace
> the macro with the function in all cases, and maybe it wouldn't slow
> things down too horribly (maybe especially if you made the function
> inline). But it still doesn't change the fact that your program would be
> buggy and you'd be getting garbage output.
Uhm, I am confused here. Why cannot we change that code to report an
error?
--
Ettore
_______________________________________________
evolution-hackers maillist - [EMAIL PROTECTED]
http://lists.helixcode.com/mailman/listinfo/evolution-hackers
