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

David,

Safe "C/C++" programming means you will check.  What to do is the
question as it wont happen hardly EVER...if ever.

I would return something to the caller to indicate failure.  Such
as a NULL.  But I don't know how well RPG would handle that as
I'm not much of an RPG programmer anymore.

Bob

> -----Original Message-----
> From: c400-l-bounces@xxxxxxxxxxxx 
> [mailto:c400-l-bounces@xxxxxxxxxxxx] On Behalf Of David Gibbs
> Sent: Thursday, August 28, 2003 3:04 PM
> To: C400-L@xxxxxxxxxxxx
> Subject: [C400-L] Re: Testing malloc results for null on the 
> 400 (was: HTTP Authentication / base64 encoder?)
> 
> 
> Bob Crothers wrote:
> > Depends ...
> 
> That's always the answer :)
> 
> > If you don't mind your program failing every once in a while
for
> > no discoverable reason, then don't worry about it.  
> 
> Well, if it fails because it could not malloc some memory, 
> would there 
> be any indication of WHY it couldn't malloc the memory?
> 
> However, since I want to be a good C programmer (not that I'm 
> really a C 
> programmer at all, just hacking at it right now) ... what 
> would be the 
> best way to indicate that the routine could not malloc memory?
> 
> The prototype for the function is: char *str_base64_encode(char
*str)
> 
> The routine is being called from RPG.
> 
> 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.
>