[Fribidi-discuss] memory allocation problems

[Behdad Esfahbod]

Hi,

On Tue, 27 Nov 2001, Tomas Frydrych wrote:
> Hi there,
> > It seems that you are using fribidi-0.9.0, it has lots of bugs and 
> > memory faults, that all are fixed already, please use the latest 
> > fribidi from CVS, available at:
> 
> > fribidi will be released in a few weeks, the new version does not 
> > depend on glib, and is quite standalone.
> 
> I have just checked out the CVS version, and it does not compile. 

Why?! what's the problem/errors?

> Also, it still depends on glib; the only difference in this respect is 
> that the glib memory management functions are now also available 
> in fribidi_mini_glib. This leaves me exactly where I was earlier 
> today -- I cannot compile with the mini-glib because the typedef's 
> with names like gchar found in fribidi_mini_glib.h and the g_ 
> functions clash with the typedefs in regular glib.h.

Right, I'm doing the job to remove glib, but it is not done yet, well, 
maybe this weekend (I mean by friday night) its done.

> And I cannot 
> compile with regular glib, because the g_mem_chunk allocation 
> clashes with the standard malloc allocation. And so I have to hack 
> the whole thing.

What? I cannot understand the problem with linking with glib, can you 
explain more please?

> I am also not too thrilled seeing that FriBidiCharType is now 
> defined using #define rather than enum, but I assume there must 
> have been reasons for that.

Yes, there was a problem with compiling fribidi on 16bit processors, 
that usually do not allow long enums.

> Also, could I ask again that an extra value is added 
> FriBidiCharType that an application could use to indicate that a 
> variable has not been properly initialised? In the AbiWord fork I call 
> it FRIBIDI_TYPE_UNSET, but any other name will do. Without it I 
> will have to continue forking fribidi.

Yes! I have it in mind and have done it in my local copy, to check in, 
I have condsidered the sign bit for that, I mean all negative values 
are going to be considered invalid (or unset by your definition), but 
algorithm does not check for them, then you just should not ever pass 
them to fribidi's functions.

> Thanks for help
> 
> Tomas

Yours,
-- 
Behdad
7 Azar 1380, 2001 Nov 28

[Finger for Geek Code]