Thank you all for the excellent suggestions, I'll be looking into all
of your references this afternoon. Regarding my initial question, I
understand I don't need free.
My real problem was if I needed to include standard libraries after
including system.h or if system.h would provide me free from s
On 3/8/07, Diego Novillo <[EMAIL PROTECTED]> wrote:
Another convenient way of allocating a pool of memory is to use obstacks
(See libiberty/obstack.c).
Though alloc-pool might be a better idea than obstack, see
alloc-pool.[ch]. As alloc-pool contains checking code while obstack
does not.
-- P
Dave Korn wrote on 03/08/07 07:30:
> (Also, bear in mind that if you want your new pass to work correctly with
> pre-compiled headers, you really ought to be using Gcc's garbage-collected
> memory management facilities. See
> http://gcc.gnu.org/onlinedocs/gccint/Type-Information.html#Type-Infor
On 08 March 2007 11:46, Paulo J. Matos wrote:
> Hello all,
>
> when using functions from libiberty, I'm for example using xstrdup and
> xmalloc but free is not defined as free or xfree afail nor strlen so
> how should I include things? Before system.h and then standard libs or
> the other way aro
