At 03:59 PM 3/28/00 -0500, [EMAIL PROTECTED] wrote:
> "Craig A. Berry" <[EMAIL PROTECTED]> writes:
> > At 01:52 PM 3/28/00 -0500, Charles Lane wrote:
> >
> >>+ I'm using LIB$(GET|FREE)_VM here so that we can allocate and
> deallocate
> >>+ inside an AST routine without worrying about reentrancy and which Perl
> >>+ memory allocator is being used.
> >
> > Mixing these with malloc() used to be a no-no; does the fact that you have
> > them in an AST routine allow you to dodge that restriction?
>
>Do you mean "don't use one to allocate and the other to free"? I do keep
>them separate in that regard (i.e., buffers from LIB$GET_VM are freed using
>LIB$FREE_VM).
It's got to be "alloc and free with the same library". The Vax C RTL was
pretty sloppy, but I can't imagine it completely forbidding the use of
LIB$GET_VM. Well, I can, but that's going a little far even for it. (Might
mess up sbrk, though, which could be why it was an issue)
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
