Re: [Cgdb-devel] C ADT library

[Bob R. <bo...@br...>]

> >Are you interested in starting libcontain with the data structures from
> >Glib? But changing the interface, typedef's, ... so that you can change
> >the implementation later to whatever you want.
> >
> >I would be interested in porting away the code and committing them to
> >libcontain.
> >
> >CGDB, could then merge libcontain into it every time some nice new
> >improvement came along.  That way, you would get a head start on the
> >data structures you need, and CGDB could use libcontain.=20
> >
> >It could be a marvelous relationship :)
> >
> That would place libcontain under GNU LGPL (it is under a BSD-GPL double=
=20
> license right now) but it would definitely get libcontain a lot further=
=20
> on its road.
> (... thinking ...)
>=20
> yeah, why not :)
>=20
> I'll have to isolate the glib code from the rest of my code pretty=20
> clearly, though, so I don't end up re-licensing Jail-ust, but LGPL is=20
> not as virulent as GPL so it should be OK.
>=20
> I'll get right on it.

I already ported glist, ghash and gtree out of Glib. I removed all of
the typedef's, things like typedef void* gpointer. I am now commenting
the interfaces with doxygen style comments.

These are the 3 ADT's that CGDB will need right away.
I could have them "CGDB" ready in a few days, then I could give them to
you to do what you want with after that.

Does this sound good? The only reason I already started porting these 3
is because I need them before I can begin implementing libkui.

To be perfectly honest, I am glad we didn't link in glib. The interface
isn't all that great, and some of the data structures I think are
implemented poorly. Also, functions like "g_tree_remove" do not return
an error value. So, you have no idea if the remove was successful or
not. These types of things I do not particularly like and didn't really
expect from a library as popular as Glib.

Thanks,
Bob Rossi