Why must Palm try to be unique? Been pulling my hair out for several hours over strange Metrowerks compile errors. Been cursing Metrowerks then figured out the problem was Palm's fault. It is such a beautiful platform that they decided to defy the C/C++ world by having their own function name that are slightly off from ANSI. To alleviate the C/C++ developers' frustration, they defined macros that maps ANSI to their own functions. This really makes life easier when you are free from the burden of naming your functions with silly names like close() or open() since sys_socket.h defines macros that maps close() and open(). These were macros instead of inline functions because that would be too ANSI and developer friendly. What to do? Rename my functions? Well that would break the code for those silly Windows and Unix developers who use the same code and are burdened with such naming anachronisms. Guess it's time to practice the art of ifdef'ing. Who needs standards, right? Thank you, Palm for relieving me of these silly naming conventions. Thank you very much!
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
