Martin Jambon wrote:
 > Nice, but in theory, it may create identifiers that are bound to an
> incorrect value when the programmer forgot to define such a value.
> 
> For example, module A should provide A.x to module B (= another .ml file).
> If the programmer forgets to define A.x, the compiler should report the
> error at the time of compiling b.ml. But if some camlp4 extension
> operating over a.ml introduces a variable A.x and by chance it has the
> same type as the expected A.x, then the compiler will remain silent and
> B will use the wrong value for A.x.
> 
> 
> Martin
> 
It seems to me that the only way to satisfy this requirement involves a
distinct namespace for these variables.  Maybe
Camlp4.Unique_identifiers.<generated identifier>?

But this seems isomorphic to the simpler solution of claiming a portion
of the identifier space: __camlp4_unique_identifier_<generated identifier>.

E