on Windows GlobalAlloc is preferred because that is something that can be used by the caller. RexxAllocateMemory() and RexxFreeMemory() are fairly recent additions to ensure the proper mechanism is used. Nothing should be changed here.
Rick On Sat, Nov 27, 2021 at 2:10 PM Erich Steinböck <erich.steinbo...@gmail.com> wrote: > On Windows RexxAllocateMemory uses GlobalAlloc, whose docs state "The > global functions have greater overhead and provide fewer features than > other memory management functions. New applications should use the heap > functions .." > > The mentioned heap functions are HeapAlloc/HeapFree, but require an > initial HeapCreate and a final HeapDestroy. > > On Unix RexxAllocateMemory uses standard malloc. > > Might it be worth migrating away from GlobalAlloc? If so, to which of the > two options? > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel >
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
