From: "David McClain" <dmcclain@azstarnet.com>
To: <caml-list@inria.fr>
Subject: Secrets of OCAML
Date: Wed, 12 Jan 2000 20:53:32 -0700 [thread overview]
Message-ID: <001501bf5d79$ce98a740$250148bf@vega> (raw)
It may not seem obvious until you try to implement similar functionality in
a language of your own. But the need to prefix a label with the module name
derives from the simple fact that the module is the place where the label is
defined... After you realize that, it is a simple matter to create compound
names of any depth crossing any number of module boundaries in the process.
Unless a module is "Used" in the sense of importing all of its symbols into
your current module, you must refer via the definining module name. It
really is quite simple after all...
- DM
reply other threads:[~2000-01-13 16:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='001501bf5d79$ce98a740$250148bf@vega' \
--to=dmcclain@azstarnet.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;
as well as URLs for NNTP newsgroup(s).