Version française
Home     About     Download     Resources     Contact us    

This site is updated infrequently. For up-to-date information, please visit the new OCaml website at

Browse thread
[Caml-list] monomorphic restriction or typing/scanf bug?
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: -- (:)
From: Chris Hecker <checker@d...>
Subject: Re: [Caml-list] monomorphic restriction or typing/scanf bug?

>The standard workaround is to use nameless ones.

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

>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,

To unsubscribe, mail Archives:
Bug reports: FAQ:
Beginner's list: