Ulrich Drepper wrote: > > > > If 'errno' is a function call, how the heck does 'errno =3D 0;' do > > anything? If it works because the compiler/system treats errno > > as a integral value, then everything else is moot. > > Come on people, just look at the implementation of a decent system: > > #define errno (*__errno_location ()) > > is what glibc does. >
This issue was that we needed to jump through all kinds of hoops because errno could be "anything". The counter argument was that as far as usage and implementation, errno is seen as a scalar integer value which significantly bounds the "problem." How errno is "really" implemented is immaterial. -- =========================================================================== Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/ "A society that will trade a little liberty for a little order will lose both and deserve neither" - T.Jefferson
