caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Maxence Guesdon <maxence.guesdon@inria.fr>
To: "Luca de Alfaro" <luca@dealfaro.org>
Cc: "Till Varoquaux" <till.varoquaux@gmail.com>, caml-list@yquem.inria.fr
Subject: Re: [Caml-list] ocamlp3l and command line options: how?
Date: Wed, 22 Aug 2007 08:06:27 +0200	[thread overview]
Message-ID: <20070822080627.3d267b2c@tintin.inria.fr> (raw)
In-Reply-To: <28fa90930708211830r28a22dc0q82e4b480c312df87@mail.gmail.com>

On Tue, 21 Aug 2007 18:30:52 -0700
"Luca de Alfaro" <luca@dealfaro.org> wrote:

> Thanks, but the problem seems to be the opposite one.... ocamlp3l also
> uses Args, and once I tell it to parse the command-line options, the
> options such as -rootp3l do not seem to work any more.  The problem is
> not that I need to avoid -rootp3l; the problem seems to be that the
> ocamlp3l runtime doesn't see its own options any more...

Hello,

You can add options with the Command_options.add function.
Exemple:

let my_options = [
  "-nl", Arg.Unit print_newline, "just print a newline" ;
  (* other options ... *)  
]
in
List.iter (fun (o,spec,s) -> Command_options.add o spec s) my_options;

They will be handled when ocamlp3l analyzes the command line.

Maxence
> 
> Luca
> 
> On 8/21/07, Till Varoquaux <till.varoquaux@gmail.com> wrote:
> >
> > The Arg module use a cursor to know which argument it is is currently
> > parsing. You can therefor ignore the first argument like this:
> >
> > incr Arg.current
> >
> > before calling Arg.parse
> >
> > Cheers,
> > Till
> >
> > On 8/21/07, Luca de Alfaro <luca@dealfaro.org> wrote:
> > > I am trying to use ocamlp3l to parallelize some code.  Using the
> > skeleton
> > > paradigm was a lot of fun and quite easy, but I am stumbling on the
> > easiest
> > > of issues...
> > >
> > > My code needs some command-line options, and I am processing them with
> > the
> > > Arg package.  The ocamlp3l manual does not anything about what to do
> > > for command-line options.
> > >
> > > I cannot simly run:
> > >
> > > ./foo -p3lroot -i blah -o boink
> > >
> > > because Arg tells me that it doesn't know what to do with -p3lroot.
> > > Fine, but, then how do I do?  It's not really feasible for me to do
> > without
> > > command-line options...
> > >
> > > Many thanks in advance,
> > >
> > > Luca
> > >
> > > _______________________________________________
> > > Caml-list mailing list. Subscription management:
> > > http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> > > Archives: http://caml.inria.fr
> > > Beginner's list:
> > > http://groups.yahoo.com/group/ocaml_beginners
> > > Bug reports: http://caml.inria.fr/bin/caml-bugs
> > >
> > >
> >
> >
> > --
> > http://till-varoquaux.blogspot.com/
> >


  reply	other threads:[~2007-08-22  6:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-21 21:43 Luca de Alfaro
2007-08-21 22:21 ` [Caml-list] " Till Varoquaux
2007-08-22  1:30   ` Luca de Alfaro
2007-08-22  6:06     ` Maxence Guesdon [this message]
2007-08-22  6:21       ` Luca de Alfaro

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=20070822080627.3d267b2c@tintin.inria.fr \
    --to=maxence.guesdon@inria.fr \
    --cc=caml-list@yquem.inria.fr \
    --cc=luca@dealfaro.org \
    --cc=till.varoquaux@gmail.com \
    /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).