Hi,
If I misunderstood you, then I still misunderstand you: the App
constructor you quoted took only 1 argument (a pair), so you can't
partially apply it, and that's from the type declaration.
IOW the type declaration you quoted is *not* curried.
Now I get what you mean, and there's
bluestorm bluestorm.d...@gmail.com writes:
It was actually the case in Caml Light : each datatype constructor
implicitly declared a constructor function with the same name. I
don't exactly know why this feature was dropped in Objective Caml,
but I think I remember (from a previous discussion)
On 31-10-2010, Wojciech Daniel Meyer wojciech.me...@googlemail.com wrote:
bluestorm bluestorm.d...@gmail.com writes:
It was actually the case in Caml Light : each datatype constructor
implicitly declared a constructor function with the same name. I
don't exactly know why this feature was
On Sun, Oct 31, 2010 at 3:35 PM, Sylvain Le Gall sylv...@le-gall.net wrote:
On 31-10-2010, Wojciech Daniel Meyer wojciech.me...@googlemail.com wrote:
bluestorm bluestorm.d...@gmail.com writes:
It was actually the case in Caml Light : each datatype constructor
implicitly declared a constructor
On 31-10-2010, Lukasz Stafiniak lukst...@gmail.com wrote:
On Sun, Oct 31, 2010 at 3:35 PM, Sylvain Le Gall sylv...@le-gall.net wrote:
On 31-10-2010, Wojciech Daniel Meyer wojciech.me...@googlemail.com wrote:
bluestorm bluestorm.d...@gmail.com writes:
It was actually the case in Caml Light :
On Sun, Oct 31, 2010 at 4:08 PM, Sylvain Le Gall sylv...@le-gall.net wrote:
Function names and values are low id in OCaml (first letter must be
uncapitalized). If you try to define let MyConstr = 0 in an OCaml
toplevel, you will get a syntax error...
In unmodified toplevel, but the whole
Well
I'm just have done ubuntu package for camllight for maverick.
I add a caml_all interactive mode to camllight and backup it for lucid,
maverick and debian squeeze. With this mode, when doing
$ camllight caml_all
you can use libgraph, libnum and libunix in interactive mode.
debian
