From: "Salz, Rich" <[EMAIL PROTECTED]>

SalzR> Not if you want to maintain portable code, you can't.

No entirely true.  It's very possible to use, if you make sure you
have a standard replacement alloca() for those architecture that don't
have it.  alloca() is becoming more widespred...

SalzR> I am concerned that "we'll just always malloc" not
SalzR> become the standard behavior.  This will lead to
SalzR> memory fragmentation, etc., and ultimately poor
SalzR> performance in long-running servers.

There are other solutions, then, like keeping memory pools to make
sure we don't get that kind of fragmentation.  That will require some
extra work, however...

-- 
Richard Levitte   \ Spannv�gen 38, II \ [EMAIL PROTECTED]
Redakteur@Stacken  \ S-161 43  BROMMA  \ T: +46-8-26 52 47
                    \      SWEDEN       \ or +46-708-26 53 44
Procurator Odiosus Ex Infernis             -- [EMAIL PROTECTED]

Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.stacken.kth.se/~levitte/mail/> for more info.
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to