I have been using this for about six months in production and have not run into any disconnect cases - may be something lurking.
Didn't cc - thought this was offline -----Original Message----- From: Sam Tregar [mailto:[EMAIL PROTECTED]] Sent: Sunday, January 20, 2002 5:20 PM To: Stanley, Jack Cc: [EMAIL PROTECTED] Subject: RE: Bang returns On Sun, 20 Jan 2002, Stanley, Jack wrote: > Thanks - my miss - I generally call other API routines - and get other error > codes in addition to errno - so I setup this method to return what made > sense to my caller. > > I never found a direct reference to setting it - was playing with the > duality of variables and decided to see if I could find it and set it - > worked. You might consider using a separate channel for application-specific error codes. Maybe exceptions of some flavor or a dedicated error variable ($My::Project::errno)? I wonder if setting $! explicitly from C breaks its link to errno... What happens if you try to use it normally after calling your routine? -sam PS: Your replies to me are missing a CC: [EMAIL PROTECTED]
