Reentrant functions and memory allocation

From: fmassei@xxxxxxxxx
Date: Sun, 30 Mar 2008 05:45:37 -0700 (PDT)

Dear all,
I'm trying to put some old code in a portable, cross-platform library
and I'm facing a big problem: is there a standard, platform-
independent way to write a reentrant function that allocate dynamic
memory? In other words: is it safe to use malloc() or free() in a
thread-safe function?
Thank you,
Francesco
.

Follow-Ups:
- Re: Reentrant functions and memory allocation
  - From: Tomás Ó hÉilidhe
- Re: Reentrant functions and memory allocation
  - From: CBFalconer
- Re: Reentrant functions and memory allocation
  - From: Eric Sosman
- Re: Reentrant functions and memory allocation
  - From: santosh
- Re: Reentrant functions and memory allocation
  - From: Flash Gordon

Prev by Date: Re: ?: as an lvalue
Next by Date: Re: Experiences using "register"
Previous by thread: ?: as an lvalue
Next by thread: Re: Reentrant functions and memory allocation
Index(es):
- Date
- Thread

Relevant Pages

Re: Steve Jordan w/ John Mayer on Kimmel last night
... One kit was a standard 4 piece facing the audience and the other was the two piece just to his left facing Mayer and Paladino. ...
(rec.music.makers.percussion)
Reenter old values
... I'm facing the next problem, ... When having a label on a form with standard Top = 40 ... Is there a code to get the standard Object Inspector ... Thanks Sander ...
(alt.comp.lang.borland-delphi)