Are you the same Barbara Morris who worked at the University of Maryland
Baltimore two or three years ago?

Please let me know.

Thanks

Armando
(410) 706-1664
adias@xxxxxxxxxxxxx

========================================================================
===

-----Original Message-----
From: Barbara Morris [mailto:bmorris@xxxxxxxxxx] 
Sent: Monday, July 14, 2003 7:12 PM
To: C400-L@xxxxxxxxxxxx
Subject: [C400-L] Re: Trap for errors

Bobby.Hicks@xxxxxxxxxxxxxxxx wrote:
> 
> I am new to C, and I'm hoping that someone can help me.  How can I
check
> for errors during procedure/program flow.  Basically I have a
conversion
> routine to convert a binary field to either a packed or zoned field.
I
> want to ensure that an overflow problem or something similar does not
give
> a hard error, instead I want to return an error code to the calling
> program.  Thanks for any help  you can provide me.
> 
> Bobby.

Bobby, C's standard exception handling is through "signals", using
functions setjmp, signal and longjmp.

ILE C also has #pragma exception_handler.

You could also use ILE Condition Handlers - see functions CEEHDLR and
CEEHDLU.

I personally find the #pragma exception_handler to be the easiest to
use, but if you want to learn something that's standard for C, learn
about signals.

_______________________________________________
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.



This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].