List Info

Thread: Allocating memory in parser.c




Allocating memory in parser.c
country flaguser name
Germany
2007-03-31 07:19:29
This is not of concern to the xattr support, but the
question popped up
nevertheless:

Is there a place to free memory that has been allocated in a
parse_*
function?

  Leslie

-- 
NEW homepage: https://
viridian.dnsalias.net/~sky/homepage/
gpg --keyserver pgp.mit.edu --recv-keys DD4EBF83

_______________________________________________
Bug-findutils mailing list
Bug-findutilsgnu.org
h
ttp://lists.gnu.org/mailman/listinfo/bug-findutils

Re: Allocating memory in parser.c
user name
2007-03-31 11:05:41
On 3/31/07, leslie.polzergmx.net
<leslie.polzergmx.net> wrote:
>
> This is not of concern to the xattr support, but the
question popped up
> nevertheless:
>
> Is there a place to free memory that has been allocated
in a parse_*
> function?

There isn't.  This is mainly because in the current
implementation of
find this doesn't need to happen.   Adding such a feature
would mean
that the implementation would need to deal correct with the
three
outgong links from each node (pred_next, pred_left and
pred_right).

It seems to me that a predicate being removed would have to
have no
left or right children.   As for pred_next, it's in a sense
a shame we
have it, because it is pretty much only used at parse time,
after we
have read all the tests from the command line but before we
have built
the parse three.

James.


James.


_______________________________________________
Bug-findutils mailing list
Bug-findutilsgnu.org
h
ttp://lists.gnu.org/mailman/listinfo/bug-findutils

[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )