docs? I've read the companions pdf and reference. Knew about the macros. Don't recall it saying "don't name your functions open(), close(), rename()". Don't recall it saying define IGNORE_STDIO_STUBS if you want to name functions with the same name as stdio functions.
Benefits? No benefits in relation to developer satisfaction. Of all the PDA developers I've come across, the opinion is universal. Palm very well knows what that is. Their slide in marketshare is directly related to their poor developer relation and support. We all know that Palm is the Netscape/Apple/SUN of the PDA world. They spent too many years complacently riding their initial high. They need to understand that MS dominance was built on underhandedness AND great developer relations and support. Palm needs to get with the times. Perhaps more up to date example code would help. Those examples, circa Palm Pilot professional, just don't cut it anymore. Hope you don't get the wrong idea. Not trying to start an argument, just venting. This is the only platform I feel the need to vent whenever I do work on it. "Chris Antos" <[EMAIL PROTECTED]> wrote in message news:114199@palm-dev-forum... > > To be fair, had you read the docs up front, you wouldn't have been confused > at all. :-) > > Also, please recall that "inline" is a C++ thing (yes most compilers have an > option to enable certain C++ extensions in C, but you made such a big deal > about ANSI standards that it seems you aren't the sort of person who would > condone using the non-ANSI extensions anyway). > > I could go on with several other reasons why it's not as bad as you make > out, and even several reasons why it's actually beneficial. If you think on > it a while (or read up on it) you can come up with some of the reasons > yourself, so I'll leave that to you. > > > "Loc" <[EMAIL PROTECTED]> wrote in message > news:114187@palm-dev-forum... > > > > 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/
