Manoj Srivastava <[EMAIL PROTECTED]> writes: > ---------------------------------------------------------------------- > 1.6 Definitions of terms > > ... Permissible undefined behaviour ranges from ignoring > the situation completely with unpredictable results, to ... > ______________________________________________________________________ > > Please show why my statement is incorrect wrt to the above > statement from the C standard. I said: "Corupting memory is not > acceptable behaviour! (Unless you document this)". The standard says > "permissible undefined behaviour ..." > > I understand that it is fashionable in comp.lang.c to say that > undefined behaviour means "It can corrupt memory, re-format your hard > disk, or make monkeys fly out of your nose; all of these are ISO C > compliant.", but the standard does make a statement about permissible > undefined behaviour, and unless such action is documented, it is not > permitted by the standard.
Making monkeys fly out of my nose certainly sounds unpredictable to me. greg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
