caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Benjamin Greenman <blg59@cornell.edu>
Cc: Kenichi Asai <asai@is.ocha.ac.jp>, Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] Labels at the module level?
Date: Tue, 23 Jun 2015 04:46:21 -0400	[thread overview]
Message-ID: <CAAtAoRoeDcKr2LU0Z=nS6k6FXab=SnOGaMy4XHX+Nkh1R2g68w@mail.gmail.com> (raw)
In-Reply-To: <CAAxsn=Gf+Kp+K+OBF65N_6CN4Lf1v-4WC0harO8jUhj0eb46hA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2113 bytes --]

Instead of making a functor, you could try a first-class module:

module type Person = sig
  val name : string
  val age : int
end

let make_person ?(name="anon") (age : int) : (module Person) =
  (module struct
    let name = name
    let age = age
  end)

On Tue, Jun 23, 2015 at 4:43 AM, Jeremy Yallop <yallop@gmail.com> wrote:

> On 23 June 2015 at 09:26, Kenichi Asai <asai@is.ocha.ac.jp> wrote:
> > Using labeled arguments, one can supply default values for unspecified
> > arguments:
> >
> > let f ?(x = 3) y = x * y
> > in f 5
> >
> > will return 15 without specifying the value of x at the second line.
> > Is there a way to do a similar thing at the module level?  Namely, I
> > want to define a functor that accepts a module of sig:
> >
> > module type A_t = sig
> >   val x : int
> >   val y : int
> > end
> >
> > but if the user did not specify some of the values in the signature,
> > some default values will be used.
> >
> > Background: in the universe library for OCaml:
> >
> > http://pllab.is.ocha.ac.jp/~asai/Universe/
> >
> > one specifies various handlers for events (such as tick, mouse, and
> > key events).  Currently, these handlers are registered to the big_bang
> > function that accepts them using labeled arguments (with default
> > values).  I wonder if I can specify the interface as a module
> > signature and let the user write a module of that signature but only
> > those handlers that the user is interested in.
>
> Alain Frisch once had a patch to add exactly what you're asking for as
> a language feature:
>
>      http://alain.frisch.fr/soft.html#patches   (Scroll to 'optional
> fields in modules')
>      http://alain.frisch.fr/info/patch-option-announce
>
> In the absence of such a feature, one approach is to use 'include' to
> provide the defaults:
>
>     module M
>       include M_defaults
>       let y = 3
>    end
>
> Jeremy.
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>

[-- Attachment #2: Type: text/html, Size: 3927 bytes --]

  reply	other threads:[~2015-06-23  8:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-23  8:26 Kenichi Asai
2015-06-23  8:43 ` Jeremy Yallop
2015-06-23  8:46   ` Benjamin Greenman [this message]
2015-06-24  0:25 ` Kenichi Asai
2015-06-26  8:12   ` Ben Millwood
2015-06-23  8:50 Oleg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAAtAoRoeDcKr2LU0Z=nS6k6FXab=SnOGaMy4XHX+Nkh1R2g68w@mail.gmail.com' \
    --to=blg59@cornell.edu \
    --cc=asai@is.ocha.ac.jp \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).