I did some more investigation into this bug and the results were truly
surprising.  It turns out that this is not an incrementality bug in the usual
sense of the word.  It can be reproduced without any changes to any classes
or to the configuration file, after initial compilation.

To reproduce the bug:

1. Start estudio and compile with the attached class and config file (melt).
   The class just has a creation procedure that does `print (out)'.
2. Finalize, keeping assertions.  No need to do C compilations.
3. Freeze, with C compile.  C compilations fail due to a syntax error in the
   code generated for {TEST}.make.  There is an extra parenthesis.

If you delete the EIFGENs tree and freeze from scratch with C compilation, it
works fine.  Very strange.

I added eweasel test incr325 for this bug, but for reasons I don't understand
the test always passes.  One has to do the above steps in one estudio session
to generate workbench C code with a syntax error.

I think this deserves to be investigated before 6.4, if at all possible.  We
use "finalize and keep assertions" in some of our productions apps.