RE: getting errno and its text description

Hello Steve,

You wrote:
>I would think that the use of NOOPT here is overkill since once this
>exception handling code starts to run the exception has, by definition,
>already occurred.  The NOOPT is only needed within the code that the
>exception has jumped over as the unmonitored exception falls down the call
>stack.

Well, since optimization is probably performed at the procedure level, and 
since there is nothing in the procedure that indicates errno changes, it is 
possible that the optimizer might make a bad choice. However, since the 
example procedure is fetching the address of errno (which won't change 
anyway) then it is unlikely that any optimization would cause a problem. 
Perhaps Carsten was simply being cautious?

Regards,
Simon Coulter.
--------------------------------------------------------------------
   FlyByNight Software         AS/400 Technical Specialists       
                                                                  
   http://www.flybynight.com.au/                                  
   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\   
   Fax:   +61 3 9419 0175   mailto: shc@xxxxxxxxxxxxxxxxx   \ /   
                                                             X    
                 ASCII Ribbon campaign against HTML E-Mail  / \   
--------------------------------------------------------------------