🚀 go-pugleaf

	Re: Declaration after use is an abomination, 
	    and should not bear consideration.

Yeah? And so's your mother! (Proof by assertion refuted by childish ad
hominem attack. Now that I've satisified net protocol...)

What's wrong with declaration "after use"? Especially for procedures
and the destinations of pointer types, declaration after "first
mention" is often a natural programming style. It does make single pass
compilation more difficult, sometimes impossible, and has performance
implications for any compiler that has to translate the language that
allows it. However declaration after use is not the obvious abomination
you would try to hand wave us into believing.

If claim that declaration before use results in more correct, easier to
maintain programs, I will reply that the easiest to maintain large
programs I ever worked on had all procedures declared in strict
alphabetical order. That sure made a given procedure easy to find.

One pass compilers are a boon to compiler writers and people who have
to run on small machines. For them a one pass compiler is often the
only possibility. For others who have large machines, and want an easy
to use language, but don't want to sacrifice correctness or efficient
object code, a multi-pass compiler is often the right thing.

	-- Charles