From: Richard Jones <rich@annexia.org>
To: Alex Baretta <alex@barettadeit.com>
Cc: Ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] BCP relating to -pack?
Date: Thu, 26 May 2005 13:12:01 +0100 [thread overview]
Message-ID: <20050526121201.GA16312@furbychan.cocan.org> (raw)
In-Reply-To: <42959F7A.7020908@barettadeit.com>
A better way to create a hierarchical namespace seems to be to use
some character _other than_ '.' (dot) to separate the levels.
For instance:
Pxp_document
Net_httpclient (nearly)
This allows a third party to come along and add packages to the same
"namespace", eg. Pxp_myextension.
Using dot / -pack doesn't allow extension and doesn't allow the package
to be spread over several cma files.
Rich.
(I'm not claiming that I've used this convention in my own packages,
but I ought to have done ...)
--
Richard Jones, CTO Merjis Ltd.
Merjis - web marketing and technology - http://merjis.com
Team Notepad - intranets and extranets for business - http://team-notepad.com
next prev parent reply other threads:[~2005-05-26 12:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-26 10:05 Alex Baretta
2005-05-26 12:12 ` Richard Jones [this message]
2005-05-26 12:38 ` [Caml-list] " Alex Baretta
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=20050526121201.GA16312@furbychan.cocan.org \
--to=rich@annexia.org \
--cc=alex@barettadeit.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).