Frank, >(By the way, the program text above compiles and runs without warning or >error on >my Linux workstation using the default settings for the system's usual tools.) I am being slow this week. Programmers don't have understanding, they have expectations. What is the first thing that every compiler writer learns? Try and compile the source so that it delivers the answer that the user expected (on pain of going out of business through lack of customers). What is a recurring theme in C standard committee discussions? The principle of least surprise. C programmers will probably have an expected idea of how something will work, lets not surprise them by making it work differently. Franks program will work on most compilers without complaint. Those tiresome warnings complaining about 'uninteresting' issues being switched off by default (try the -Wall option Frank) because they might clash with the users view of the source. derek -- Derek M Jones tel: +44 (0) 1252 520 667 Knowledge Software Ltd mailto:[EMAIL PROTECTED] Applications Standards Conformance Testing http://www.knosof.co.uk - Automatic footer for [EMAIL PROTECTED] ---------------------------------- To unsubscribe from this list, mail [EMAIL PROTECTED] unsubscribe discuss To join the announcements list, mail [EMAIL PROTECTED] subscribe announce To receive a help file, mail [EMAIL PROTECTED] help This list is archived at http://www.mail-archive.com/discuss%40ppig.org/ If you have any problems or questions, please mail [EMAIL PROTECTED]
