🚀 go-pugleaf

> >   a == b is for comparison. Its value is 1 if they're equal, 0 if not.
> >   a := b is for assignment. It sets a to b and has value a.
> >   a = b is for assignment. It sets a to b and has no value.
> 
> Good idea. PL/M ... does something like this ...


I like the Q and PL/M features, but they don't stop me from typing:

	a == b + 1;	/* OOPS, I mean't to assign to a */
or
	if (a := b) ..	/* OOPS, I only wanted to compare them */
not to mention
	a = b++ * b++;


What we *really* need are compilers that issue warnings such as:

test.c: line 7: result of comparison unused!

test.c: line 8: assignment result used in boolean context,
	did you mean ((a := b) != 0), or (a == b)?

test.c: line 9: b evaluation order undefined

If our compilers did that there would be much
less debate about = and == and := in the C language.
And fewer frustrated programmers.

	Tom Truscott