BUGS

	UNRESOLVED BUGS

	Thanks to all submitters!


	*** Submitted by Warren Toomey in 9/2019

	//-comments in macros will mess up macro expansion. For
	instance:

	#define FOO 4 // 4 foos in every bar

	expands to

	printf("%d\n", 4 // 4 foos in every bar);

	which is obviously a bad idea!
	(So are //-comments. Just saying!)


	*** Submitted by Volkmar Klatt in 12/2016

	main() {
	    char c;
	    int	 i;
	    i = (c = -777);
	    printf("%d\n", i);
	}

	Prints -777, but should print 247, because c = (-777)&0xff.


	*** Submitted by Alexey Frunze in 09/2016

	printf("%x", -1); prints a negative decimal number, which it
	shouldn't according to K&R2.


	*** Submitted by Quan Tran in 10/2015

	Dont miss his improved Go version of SubC at:
	https://github.com/qeedquan/gosubc

	The SubC bootstrap compiler generated by gcc/clang uses
	4-byte int, so it will generate wrong code for x86_64
	regarding numbers out of 4-byte range, so the asm will
	mismatch against the compiler. However, the final scc built
	from the scc0 and scc1 bootstrap will use 8-byte int on
	x86_64, so that will be correct.

	SubC does not support passing struct/unions as values, but it
	allows you to declare it in function parameters, e.g.:

	void f(struct foo x) {}

	Switch statements may contain duplicate cases.

	SubC allows externs in local declarations to be initialized:

	void f() { extern int a = 10; } /* should not be allowed! */

	SubC can only index arrays using indexes of int types, e.g.:
	given
	int  a[10], b[2];
	char x[10];
	a[x[0]] does not work but a[b[0]] does work even though x[0]
	does generate a valid integer index. Workaround: a[x[0]+0],
	which will promote x[0] to int.

	SubC currently allows any unary ops on any types, even on
	structs: e.g.:

	struct file f; !f;