> -----Original Message-----
> From: Paul Taffel [mailto:[log in to unmask]]
>
> I think you may need to create an XL, create an NM function
> that returns
> the current
> value of errno, and call this NM procedure from your CM code.
>  There again,
> there may
> be an easier way of getting to it from CM...  There may well
> be a function
> already located
> within XL.PUB.SYS or NL.PUB.SYS that you could call, but I
> can't find it.
>
> Paul Taffel
> ORBiT Software     (310) 276 9003

which boils down to "it's going to be a headache" :)

Actually, I'll be doing this in SPLash!, so perhaps it isn't as difficult as
all that [i.e., I can call the functions directly, for the most part]  I
suppose making a COBOL or C subprogram to "do the dirty work" of checking
and acting upon the "errno" variable isn't as bad, but it's a kludge no
matter how you look at it...

> At 06:35 PM 10/29/99 -0400, you wrote:
> >I think I'm running into a conceptual problem here -- accessing the
global "errno" variable from an SPL program
[...]
> >[or is doing SOCKET I/O in SPL too much of a headache to be
> worth it?    The
> >long term answer to my situation is to re-write the SPL
> program in C, but
> >time constraints prohibit that at the moment -- gotta make a
> 6000+ line SPL
> >program work WITH "sockets" by the end of the week...]
>