From: Martin DeMello <martindemello@gmail.com>
To: Pat Johnson <johnson@crans.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] writing a very basic plugin system
Date: Mon, 16 Jan 2012 20:09:59 -0800 [thread overview]
Message-ID: <CAFrFfuHLmJtZO5zCCnQhXpLBP7n3Lwb3phqmDKnKD41V=wkrFA@mail.gmail.com> (raw)
In-Reply-To: <4F14DBDC.5080600@crans.org>
Perfect, thanks! Here's the complete working example (with help from
http://caml.inria.fr/pub/docs/manual-ocaml/manual021.html#toc81):
module type Plugin =
sig
val usage : unit -> unit
val handle : string list -> unit
end;;
module A = struct
let usage () = print_endline "usage of A"
let handle args = print_endline "hello from A"
end
module B = struct
let usage () = print_endline "usage of A"
let handle args = print_endline "hello from B"
end
let handle m ?(args = []) () =
let module Plug = (val
begin
match m with
"a" -> (module A: Plugin)
| "b" -> (module B: Plugin)
| _-> raise Not_found
end : Plugin)
in match args with
[] -> Plug.usage ()
| xs -> Plug.handle xs;;
let _ =
handle "a" ();
handle "a" ~args:["foo"] ();
handle "b" ();
handle "b" ~args:["foo"] ();
handle "c" (); (* => error *)
martin
On Mon, Jan 16, 2012 at 6:24 PM, Pat Johnson <johnson@crans.org> wrote:
> Le 17/01/2012 01:04, Martin DeMello a écrit :
>
>> What is the best mechanism to write the following basic plugin system?
>> Plugins should provide two functions, `usage ()` and `handle :
>> [string] -> unit`, and the main interpreter will receive args of the
>> form `plugin-name [arg1; arg2; ...]. The problem with the main handle
>> function below is that it's twice as long as necessary - I should be
>> able to capture the pattern "if there are 0 args call usage else call
>> handle" more succinctly. Ideally, I just want to have a mapping of
>> plugin name to plugin and have the rest of the code handled
>> generically.
>
>
> This can easily be dealt with 3.12 capabilities :
>
> module type Plugin =
> sig
> val usage : unit -> unit
> val handle : string list -> unit
> end;;
>
> (* let's assume A and B are declared accordingly *)
>
>
> let handle m args =
> let module Plug = val
> begin
> match m with
> "a" -> A
> "b" -> B
> | _-> raise Not_found
> end : Plugin
> in match args with
> [] -> Plug.usage ()
> | xs -> Plug.handle xs;;
>
> Hope this helps,
>
> --
> PJ
>
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa-roc.inria.fr/wws/info/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
prev parent reply other threads:[~2012-01-17 4:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 0:04 Martin DeMello
2012-01-17 2:24 ` Pat Johnson
2012-01-17 4:09 ` Martin DeMello [this message]
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='CAFrFfuHLmJtZO5zCCnQhXpLBP7n3Lwb3phqmDKnKD41V=wkrFA@mail.gmail.com' \
--to=martindemello@gmail.com \
--cc=caml-list@inria.fr \
--cc=johnson@crans.org \
/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