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

It is absolutely critical to test malloc results on all Intel platforms.
It is absolutely critical to test malloc results IN GENERAL.

But what I'd really like to know - is there any reason for OS/400 to return 
NULL after calling for example 
 r = (char *) malloc(1000000) ;

I cannot see any reason, why malloc would return NULL, other than expiring 
address space, which is 2**64 - and I even cannot imagine, how many times I'd 
have to call abovementioned malloc, before I'll get NULL...

Jevgeni.

> -----Original Message-----
> From: David Gibbs [mailto:david@xxxxxxxxxxxx]
> Sent: 28. august 2003. A. 22:04
> To: C400-L@xxxxxxxxxxxx
> Subject: [C400-L] Testing malloc results for null on the 400 (was:
> HTTPAuthentication / 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.
> 
>