From: Thomas Fischbacher <Thomas.Fischbacher@Physik.Uni-Muenchen.DE>
To: John Prevost <j.prevost@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Arg parsing
Date: Thu, 4 Nov 2004 21:40:35 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.58.0411042138450.3293@eiger.cip.physik.uni-muenchen.de> (raw)
In-Reply-To: <d849ad2a041104072810753c71@mail.gmail.com>
On Thu, 4 Nov 2004, John Prevost wrote:
> Perhaps if you explained why you want to do this, it would be easier
> for us to help you. For example, if you're using #use to test out
> argument parsing code, perhaps this could help you:
>
> module Sys =
> struct
> include Sys
> let argv = [| "testprogram"; "my"; "arguments"; "for"; "testing" |]
> end
>
> Other than that, I'm having a *really* hard time figuring out why you
> would want to examine your command line arguments from an interactive
> program.
That's precisely what I want to do. And I do not see why I should have to
bend over backwards and write such extra code for a task as simple as that
which could be easily resolved by just making the ocaml interpreter accept
a '--' arg properly...
--
regards, tf@cip.physik.uni-muenchen.de (o_
Thomas Fischbacher - http://www.cip.physik.uni-muenchen.de/~tf //\
(lambda (n) ((lambda (p q r) (p p q r)) (lambda (g x y) V_/_
(if (= x 0) y (g g (- x 1) (* x y)))) n 1)) (Debian GNU)
next prev parent reply other threads:[~2004-11-04 20:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-26 19:56 Thomas Fischbacher
2004-10-26 20:13 ` [Caml-list] " William Lovas
2004-10-27 18:17 ` Thomas Fischbacher
2004-10-27 22:13 ` John Prevost
2004-10-28 12:44 ` Thomas Fischbacher
2004-10-28 14:56 ` John Prevost
2004-11-04 14:42 ` Thomas Fischbacher
2004-11-04 15:28 ` John Prevost
2004-11-04 20:40 ` Thomas Fischbacher [this message]
2004-10-26 21:05 ` Problem with location sejourne_kevin
2004-10-26 21:36 ` [Caml-list] " Tiago Dionizio
2004-10-26 22:33 ` Matt Gushee
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=Pine.LNX.4.58.0411042138450.3293@eiger.cip.physik.uni-muenchen.de \
--to=thomas.fischbacher@physik.uni-muenchen.de \
--cc=caml-list@inria.fr \
--cc=j.prevost@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