Steve Achelis wrote:
> Tom (and Adam Wozniak):
>
> Thanks for the clues, guys.
I love to see responses like that =)
Actually, it's bothered me (only slightly) for a while that people always post decimal
error numbers when they have problems, and not hex. i.e. ErrorBase.h is in hex, so
we should talk about error numbers in hex. HOWEVER, this should extend to the
other header files as well....
#define netErrNoInterfaces (netErrorClass | 12) //ENETUNREACH
should really read...
#define netErrNoInterfaces (netErrorClass | 0x0C) //ENETUNREACH
for SEVERAL reasons:
1) ErrorBase.h is in hex.
2) I cannot logical OR a hex number with a decimal number in my head.
3) I cannot logical OR a decimal number with much of anything in my head.
4) Logical OR two hex numbers is quick, easy, painless, especially when it's 0x??00 |
0x??
It bugs me every time I see it. It bugs me most when the error number is high.
Paying some intern engineer to "fix" the header files would be a minimal expense, and
would
save developers some nonzero amount of time. Don't know if we're at the point of
diminishing
returns or not here, however. =)
--
Adam Wozniak Senior Software Design Engineer
Surveyor Corporation
[EMAIL PROTECTED] 4548 Broad Street
[EMAIL PROTECTED] San Luis Obispo, CA 93401
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
