🚀 go-pugleaf

	I've been seeing compiler crashes (Segmentation Violation
using g++ 1.36.2 on SUN3) on the terminating semicolon of class
declarations (it prints a line number, but no message).  In several
cases, I have been able to eliminate the crash by moving a particular
method declaration to the end of the class definition.  These classes
have had only public methods, so this does not change the visibility
of the method that is moved.  After making such a change, the compiler
accepts the class definition without warnings or errors.  We have been
working successfully with these classes for quite some time, but we
have recently changed the inheritance hierarchy by introducing a new
base class.
	The reason I'm not posting a sample code that exhibits this
behavior is that it is difficult to recreate the behavior in a simple
example, and I cannot simply post large pieces of our source code.
Have other people encountered anything similar?  Should I make the
effort to recreate this behavior?  Has this already been fixed?  Is
this perhaps related to the bug I reported on 12/10 where the compiler
might crash, depending on the order in which certain functions where
defined?