× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. C400-L
  3. August 2003

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





As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.