At 02:42 PM 3/28/00 -0500, Dan Sugalski wrote:
>At 01:37 PM 3/28/00 -0600, Craig A. Berry wrote:
>>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?
>
>Should we just switch over to the LIB$ memory management stuff altogether? It'd just
>require some changes to perl's memory allocator.
Hmm. The Compaq C 6.2 manual at
<http://www.openvms.digital.com/commercial/c/5763p014.htm#memory_alloc_table>
says it's no longer a problem. It's not 100% clear when mixing malloc() and
LIB$GET_VM became ok, but the implication is that it was VAX C that had the
restriction because the C RTL at that time used LIB$GET_VM internally.
Since we don't support VAX C anymore, we're probably ok having a mix.
_______________________________________________
Craig A. Berry
mailto:[EMAIL PROTECTED]
