From: Diego Olivier Fernandez Pons <Diego.FERNANDEZ_PONS@etu.upmc.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Suggestion (was: Demande clarification nomenclature ocaml*)
Date: Fri, 19 Mar 2004 11:19:43 +0100 (NFT) [thread overview]
Message-ID: <Pine.A41.4.44.0403191118450.389240-100000@ibm1> (raw)
Bonjour,
> While waiting for nested namespaces one could do namespace-by-convention. One
> would keep INRIA (or possibly something convenient and shorter) as prefix for
> INRIA OCaml stuff, leaving other useful prefixes for the normal people. This
> namespace could then be maintained in a perlish style. Reading this list from
> time to time it is quite clear that there is a number of people who mail a
> lot to this list, who know a lot about OCaml (as far as I can judge this as
> someone who knows little about OCaml), and who would be suitable for being
> maintainers of the toplevel namespace.
Je ne comprends pas votre point : je ne parle pas d'espace de noms a
l'interieur d'un langage de programmation mais de noms exterieurement
visibles. Chez nos collegues de Haskell, leurs bibliotheques
s'appellent DData, Edison, Pancito, etc. et non HaskellDataLib,
HaskellDataLib et HaskellImages.
Diego Olivier
-------------------
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
next reply other threads:[~2004-03-19 10:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 10:19 Diego Olivier Fernandez Pons [this message]
2004-03-19 10:38 ` Wolfgang Müller
-- strict thread matches above, loose matches on Subject: below --
2004-03-19 8:50 [Caml-list] Demande clarification nomenclature ocaml* Diego Olivier Fernandez Pons
2004-03-19 9:49 ` [Caml-list] Suggestion (was: Demande clarification nomenclature ocaml*) Wolfgang Müller
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.A41.4.44.0403191118450.389240-100000@ibm1 \
--to=diego.fernandez_pons@etu.upmc.fr \
--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).