apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Bannert <aa...@ebuilt.com>
Subject Re: cvs commit: apr/memory/unix apr_sms.c apr_sms_trivial.c sms_private.h
Date Sat, 07 Jul 2001 17:55:04 GMT
> > I don't think there is any benefit to this.  But, someone else might
> > be able to chime in and say why we need this functionality.  -- justin
> how do you handle out of memory?
> palloc is not permitted to return NULL for performance reasons.  (well
> that plus the massive amounts of legacy code)
> of course this whole topic is a mess and really wants proper exception
> handling... which we don't have in a convenient form in C :)

palloc() will never return NULL? Now I'm curious how out-of-memory is
handled. I guess I (wrongly) assumed palloc() would return NULL the
way malloc() does. *shrug*


View raw message