You love talloc() :)
I talked to Tridge when he put it together, and it sounded like he put
a lot of thought in it.
But... first we need a good plan for how free memory, and after that...
glibc() buys us a lot of libraries for a single cost. The last thing
we want to do is implement several.
A good comparison is what we need... but... I am doubting that we can
get the character sets/collations from talloc (in fact looking at the
library I see that it is pretty basic).
To you does it make sense to have a mashup of glibc and talloc? It
sounds like a mess.
On Jul 13, 2008, at 11:51 PM, Stewart Smith wrote:
freeing a talloc context frees everything hanging off that context
(unless you've increased a reference count elsewhere).
you can attach destructors.
--
_______________________________________________________
Brian "Krow" Aker, brian at tangent.org
Seattle, Washington
http://krow.net/ <-- Me
http://tangent.org/ <-- Software
_______________________________________________________
You can't grep a dead tree.
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
