jacques:
>The standard workaround is to use nameless ones.

Excellent, that's a fine workaround for my case!

pierre:
>Thanks for the interesting example, that could help us to revised the
>semantics of type constraints in Caml, still having in mind that
>global and local definition should always behave the same.

No problem.  That's the part that confused me about it, since I figured any 
type restriction problem (a la the FAQ) would manifest itself both globally 
and locally (except, now that I think about it the "can't generalize ref" 
only happens globally).

Now, if only we could have local exceptions to make those "C break-like 
exception patterns" easier!

Thanks guys,
Chris


-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners