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.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
- [PATCH] Perl 5.6.0: VMS piping mods Charles Lane
- Re: [PATCH] Perl 5.6.0: VMS piping mods Craig A. Berry
- Re: [PATCH] Perl 5.6.0: VMS piping mods Dan Sugalski
- Re: [PATCH] Perl 5.6.0: VMS piping mods Craig A. Berry
- RE: [PATCH] Perl 5.6.0: VMS piping mods Jordan Henderson
- RE: [PATCH] Perl 5.6.0: VMS piping mods Dan Sugalski
- Re: [PATCH] Perl 5.6.0: VMS piping mods lane
- Re: [PATCH] Perl 5.6.0: VMS piping mods lane
- Re: [PATCH] Perl 5.6.0: VMS piping mods Dan Sugalski
- Re: [PATCH] Perl 5.6.0: VMS piping mods Dan Sugalski
- Re: [PATCH] Perl 5.6.0: VMS piping mods Craig A. Berry
- Re: [PATCH] Perl 5.6.0: VMS piping mods Dan Sugalski
- RE: [PATCH] Perl 5.6.0: VMS piping mods PVHP
