Re: [Caml-list] Optional arguments in inherited methods

[Henri DF <henri.dubois-ferriere@epfl.ch>]

> Unfortunate, but in the case of optional arguments the problem is
> not with typing but with how they are implemented: an optional
> argument of type [t] is actually a non-optional argument of type [t
> option]. They disappear automagically on application, but this means
> that None's are automatically inserted. So applying a function which has
> optional arguments is completely different from a function without
> them (even if the function call looks the same in your source code).
> 

what about optional arguments which have a default value? i would assume 
these are not implemented using options, so would that change anything 
here?

thanks
henri

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