RE: Testing malloc results for null on the 400 (was: HTTP Authentication / base64 encoder?)

David,

Depends on how stable you want your program to be.  

If you want it to be stable as a Rock, you will test for it.

If you don't mind your program failing every once in a while for
no discoverable reason, then don't worry about it.  

Bob

> -----Original Message-----
> From: c400-l-bounces@xxxxxxxxxxxx 
> [mailto:c400-l-bounces@xxxxxxxxxxxx] On Behalf Of David Gibbs
> Sent: Thursday, August 28, 2003 2:04 PM
> To: C400-L@xxxxxxxxxxxx
> Subject: [C400-L] Testing malloc results for null on the 400 
> (was: HTTP Authentication / base64 encoder?)
> 
> 
> Folks:
> 
> How critical is that the results of a malloc operation be
tested for 
> null on the 400?
> 
> I'm not allocating a huge amount of data.
> 
> The base64 code I adapted invoked some error handling routine
if the 
> malloc returned a null.  I commented that line out, and it 
> seems to work 
> fine... but is this something I have to seriously be concerned
about?
> 
> How often will a malloc of a small amount of memory fail on the
400?
> 
> Thanks!
> 
> david
> 
> 
> _______________________________________________
> This is the C programming iSeries / AS400 (C400-L) mailing list
> To post a message email: C400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/c400-l
> or email: C400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/c400-l.
>