Andreas Rossberg writes:

| In fact, it would be much more complicated. First, identifier
| status is scoped. Constructors are frequently defined locally. In
| particular, this may happen implicitly through the use of "open".
| To derive the required information you hence needed to perform a
| complete binding analysis, including modules and signatures.
| [...]

Thanks, that's a good explanation. Ocaml's case convention almost
starts to look like a good idea when you see the alternatives...

| In summary, to deal with constructor status correctly (not to mention
| stuff like datatype replication, local, records, user-defined fixity,
| etc.) you basically need half an SML frontend. It seems out of scope
| for a Camlp4 hack to be more than a simple approximation.

Can you recommend any SML frontend that I could, more or less
trivially, use to systematically munge uppercase identifier names and
spit out the program again?

John.