🚀 go-pugleaf

>|> >As someone else pointed out, bool++ is a nice shorthand for test-and-set.

I am surprised that no-one else has pointed out that test-and-set is
*WRONG* for initialisation.  This should be another nail in the coffin
of bool++.  Let me explain.

In most cases, the right way to code one-time initialisation is

	{
	    static int initialised = 0;

	    if (!initialised) {
		/* many lines of initialisation code */
		initialised = 1;
	    }
	    ...
	}

The 'initialised' flag should mean "initialisation has been COMPLETED".
If you set the flag too early, as in

	    if (!initialised) {
		initialised = 1;
		/* many lines of initialisation code */

then you _may_ never be sure that initialisation has been done.   Why?
Think about signals, signal handlers, longjmp(), and so on.

I learned about this problem only a year after I started coding C.

-- 
"conventional orthography is ... a near optimal system for the
 lexical representation of English words." Chomsky & Halle, S.P.E.
Richard A. O'Keefe; http://www.cs.rmit.edu.au/~ok; RMIT Comp.Sci.