Re: [Factor-talk] manual memory management and STRUCT:

2014-03-19 Thread Bruce & Breeanna Rennie
Good evening gentlefolks, On 19/03/14 15:42, factor-talk-requ...@lists.sourceforge.net wrote: > Message: 1 > Date: Tue, 18 Mar 2014 16:44:07 +0100 > From: Bj?rn Lindqvist > Subject: Re: [Factor-talk] manual memory management and STRUCT: > To: factor-talk@lists.sourceforge.n

Re: [Factor-talk] manual memory management and STRUCT:

2014-03-18 Thread Björn Lindqvist
2014-03-18 14:12 GMT+01:00 Jon Harper : > In this case, it's more complicated then a single with-destructor scope, > because I use the destructors to call libyaml's destroy function on the > struct, so that the same memory can be reused between the calls to libyaml > for this struct. So I really ne

Re: [Factor-talk] manual memory management and STRUCT:

2014-03-18 Thread Jon Harper
In this case, it's more complicated then a single with-destructor scope, because I use the destructors to call libyaml's destroy function on the struct, so that the same memory can be reused between the calls to libyaml for this struct. So I really need to destroy it right away before the next call

Re: [Factor-talk] manual memory management and STRUCT:

2014-03-18 Thread Björn Lindqvist
Hi Jon, 2014-03-17 21:57 GMT+01:00 Jon Harper : > Hi list, > I am working with libyaml, a C library to parse yaml docs. Some libyaml > functions give string results by malloc'ing memory and giving back pointers > to those strings in a struct. They then require the caller to call a libyaml > "destr

[Factor-talk] manual memory management and STRUCT:

2014-03-17 Thread Jon Harper
Hi list, I am working with libyaml, a C library to parse yaml docs. Some libyaml functions give string results by malloc'ing memory and giving back pointers to those strings in a struct. They then require the caller to call a libyaml "destroy" function on the struct that frees the strings. I would