On 07 May 2001 23:51:34 -0400, Ettore Perazzoli wrote:
> Su 07 May 2001 13:45:14 +0930, Not Zed ha scritto:
> > There should be little performance impact of actually having the code
> > CHECK the bloody text that its processing WHILE its doing it.
>
> Sigh, I couldn't agree more. Is there any chance that we can fix that
> code ourselves to avoid the crashes? What is so hard about it? Has
> anyone looked at the code?
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.
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.
-- Dan
_______________________________________________
evolution-hackers maillist - [EMAIL PROTECTED]
http://lists.helixcode.com/mailman/listinfo/evolution-hackers
