Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: "T. Kurt Bond" <tkb@tkb.mpl.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Wildcard expansion/command line
Date: Tue, 14 May 2002 08:52:32 -0400	[thread overview]
Message-ID: <15585.2192.709871.920355@tkb.mpl.com> (raw)
In-Reply-To: <20020514102405.1ff7a399.maxence.guesdon@inria.fr>

Maxence Guesdon writes:
> 
> > So, how does it work? 
> 
> *the shell* expands your unquoted wildcards before passing the args
> to your program.

Not so, strictly speaking.  Under MS Windows the O'Caml runtime
apparently expands wildcards itself, if the shell hasn't already.  (See
byterun/main.c:main() for the call to expand_command_line() and look 
at win32.c for expand_command_line() and its helper functions.)

What did it do under pre-X versions of MacOS?

I think that historically having the shell expand the wildcards for
the program was the *unusual* situation and having the program expand
the wildcards itself was usual.  The "program expands wildcards" has
its advantages (as anybody who has used the VMS command "$ rename
*.COM *.SAV" can attest) but having the shell do it makes most
programs simpler, which is probably why Unix ended up with the shell
doing the work.
-- 
T. Kurt Bond, tkb@tkb.mpl.com

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  reply	other threads:[~2002-05-14 12:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-14  7:50 Jens Olsson
2002-05-14  8:24 ` Maxence Guesdon
2002-05-14 12:52   ` T. Kurt Bond [this message]
2002-05-14 13:11     ` Dave Mason
2002-05-14 13:30 ` Oliver Bandel
2002-05-14 15:52 ` John Max Skaller

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=15585.2192.709871.920355@tkb.mpl.com \
    --to=tkb@tkb.mpl.com \
    --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