🚀 go-pugleaf

> There may be some point allowing a terminal "u" (or "U") to specify an
> unsigned constant, so that "1u" would be of type "unsigned int"...

There's definitely a point in allowing that - ANSI C compatibility.  From
the May 1, 1986 draft, p. 23:

	   The type of an integer constant is the first of the
	corresponding list in which its value can be represented.
	Unsuffixed decimal: "int", "long int", "unsigned long int";
	unsuffixed octal or hexadecimal: "int", "unsigned int",
	"long int", "unsigned long int"; suffixed by the letter "u"
	or "U": "unsigned int", "unsigned long int"; suffixed by the
	letter "l" or "L": "long int", "unsigned long int";
	suffixed by both the letters "u" or "U" and "l" or "L":
	"unsigned long int".
-- 
	Guy Harris
	{ihnp4, decvax, seismo, decwrl, ...}!sun!guy
	guy@sun.com (or guy@sun.arpa)