> I don't think, software is more "robust", when it ignores problems > instead of reacting to a problem. Streaming or printing a > NULL pointer > is not undefined, it's wrong. The system was told, to show a text and > there is no text, so it should tell about a problem, instead of doing > something or nothing.
Yes, that is right; and printf does tell you, it explicitly prints the text (null) to the stdout, and I imagine (but have not tested) that the function return value would also signify the fault. The iostream approach tells you something has happened *if you test the badbit* but no signifier appears on the console output, and the stream stops outputting until you clear the badbit, so I think that is actually less useful in practice than the behaviour exhibited by printf. But either way, the OP seems to resolved his problems now, so all is well... SELEX Galileo Ltd Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
