• Subject: RE: C runtime Exception Errors
  • From: Scott Mildenberger <Smildenber@xxxxxxxxxxxx>
  • Date: Mon, 14 Feb 2000 08:53:16 -0700

Not for the example given.  I was in the process of modifying the service
program and the procedure shown such that two different procedures needed to
be able to access the error field so I had moved it into the global area.

> -----Original Message-----
> From: Joe Teff [SMTP:joeteff@earthlink.net]
> Sent: Saturday, February 12, 2000 5:40 PM
> To:   MIDRANGE-L@midrange.com
> Subject:      Re: C runtime Exception Errors
> 
> Was there any particular reason that you defined error as global vs
> inside the procedure?
> 
> -----Original Message-----
> From: Scott Mildenberger <Smildenber@Washcorp.com>
> To: 'MIDRANGE-L@midrange.com' <MIDRANGE-L@midrange.com>
> Date: Monday, January 31, 2000 12:14 PM
> Subject: RE: C runtime Exception Errors
> 
> 
> >Here is an excerpt from my service program.  The value imported below
> will
> >contain the 7 character message id when an error occurs.  Feel free to
> >e-mail me if you have any other questions.
> >
> >d error           s              7    import('_EXCP_MSGID')    
> >
> >p syscall         b                   export                 
> >d syscall         pi             7                           
> >d   cmd                           *   value options(*string) 
> >                                                             
> >d system          pr            10i 0 extproc('system')      
> >d   cmd                           *   value options(*string) 
> >                                                             
> >c                   if        system(cmd) <> 0               
> >c                   return    error                          
> >c                   else                                     
> >c                   return    *blanks                        
> >c                   endif                                    
> >                                                             
> >p syscall         e                                          
> 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.