constant file with names...

[Stephen Weeks]

> I have now implemented the sanity-check for
> the constants file that we talked about earlier.
> I hope that Assert.assert will complain loud enough
> if such a check fails :)

Actually, Assert.assert is only turned on in an SML/NJ compiled MLton,
unless you compile MLton -DMLton_debug=1

> So I think 2 distinctions are needed for this bootstrapping:
> 1) Host vs. Target
> 2) Comiling the compiler itself vs. compiling an app.
> 
> But probably the distinction: "Host", "Target" and "Source"
> that I already added support for in the bin/mlton
> script is better. I think it's what gcc uses for it's
> crosscompiler bootstrapping.

I'll have to think about this some more, but I'll get back to you
by next week.