caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Richard Jones <rich@annexia.org>
To: Andreas Biegert <andreas.biegert@googlemail.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] global record
Date: Wed, 19 Jul 2006 15:07:29 +0100	[thread overview]
Message-ID: <20060719140729.GA26227@furbychan.cocan.org> (raw)
In-Reply-To: <fd0847170607190411n5ba0d21bq4da186190949c685@mail.gmail.com>

On Wed, Jul 19, 2006 at 01:11:22PM +0200, Andreas Biegert wrote:
> I am developing a bioinformatics sequence analysis application which
> contains about 20 modules. One of those modules, the 'Par' module,
> encapsulates a record of about 30 configuration parameters needed
> throughout the whole application. The parameter record is mostly
> static but some values can be overwritten by command-line options. Is
> there a way to make the (possibly modified) parameters record globally
> accessable throughout all modules? This would be much more convenient
> than having to pass the parameters record to virtually all functions
> in my application. THX for helping.

This is a bit ugly, but we use it in our Adwords API toolkit:

-------------------------------------------------- stdargs.mli
val username : string
val password : string
val client : string option
val token : string
val update : bool
val verbose : bool
val args : string list

-------------------------------------------------- stdargs.ml
let username = ref ""
let password = ref ""
let client = ref ""
let token = ref ""
let update = ref false
let verbose = ref false
let args = ref []

(* followed by some code which tries to read default values
 * from $HOME/.adwordsapidata -- code omitted
 *)

(* parse the command line parameters *)
let argspec = [
  "--username", Arg.Set_string username, "Adwords account username.";
  "--password", Arg.Set_string password, "Adwords account password.";
  "--client", Arg.Set_string client, "Adwords account client (optional).";
  "--token", Arg.Set_string token, "Adwords account token.";
  "--update", Arg.Set update, "Perform updates.";
  "--verbose", Arg.Set verbose, "Be verbose.";
]

let anon_fn str = args := str :: !args
let usage =
  Sys.executable_name ^ " [--options]"

let () = Arg.parse argspec anon_fn usage

let username = !username
let password = !password
let client = if !client = "" then None else Some !client
let token = !token
let update = !update
let verbose = !verbose
let args = List.rev !args

---

Then the code just stuff like:

  open Stdargs

  if verbose then printf "this is verbose mode\n"

Rich.

-- 
Richard Jones, CTO Merjis Ltd.
Merjis - web marketing and technology - http://merjis.com
Team Notepad - intranets and extranets for business - http://team-notepad.com


  parent reply	other threads:[~2006-07-19 14:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-19 11:11 Andreas Biegert
2006-07-19 11:42 ` [Caml-list] " Pietro Abate
     [not found] ` <3d13dcfc0607190528y624e5c9eg2c45e1cb17ec3771@mail.gmail.com>
2006-07-19 12:29   ` David MENTRE
2006-07-19 14:07 ` Richard Jones [this message]
2006-07-19 14:39   ` Yoann Padioleau
2006-07-19 14:50     ` Richard Jones
2006-07-19 15:09       ` Jean-Christophe Filliatre
2006-07-19 15:08     ` William D. Neumann
2006-07-20  7:26 ` Jeff Henrikson
2006-07-19 17:14 Eric Breck

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=20060719140729.GA26227@furbychan.cocan.org \
    --to=rich@annexia.org \
    --cc=andreas.biegert@googlemail.com \
    --cc=caml-list@yquem.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).