From: Anton Bachin <antronbachin@gmail.com>
To: Ivan Gotovchits <ivg@ieee.org>
Cc: OCaml users <caml-list@inria.fr>
Subject: Re: [Caml-list] [ANN] Namespaces – sensible file naming for OCaml projects
Date: Mon, 29 Feb 2016 12:45:03 -0600 [thread overview]
Message-ID: <4C6ACEE0-9F61-431D-8FD1-1FE88E5142FA@gmail.com> (raw)
In-Reply-To: <CALdWJ+ydYm4wQkKkm17gHCZTmRnwYxLnemabm90gngCeTZVaYg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2048 bytes --]
Thanks Arto, Ivan.
The question about Merlin is a good one. I better start using Merlin
myself, because I don’t know the answer. I suppose if Merlin reads
things from src/ (or lib/, or whatever) in a project, then it shouldn’t
work. But if Merlin reads from _build/, as I would think it does, then
it “should" work. But I don’t know either way at the moment. It will
probably take some time for me to set Merlin up, but I will look into
it.
Best,
Anton
> On Feb 29, 2016, at 12:37, Ivan Gotovchits <ivg@ieee.org> wrote:
>
>
> Hi Anton!
>
> It is a great project!
>
> But nowadays I always want to know, does it work with merlin?
>
> Regards,
> Ivan
>
> On Mon, Feb 29, 2016 at 11:40 AM, Anton Bachin <antronbachin@gmail.com <mailto:antronbachin@gmail.com>> wrote:
> Hello,
>
> I would like to announce the release of Namespaces, an Ocamlbuild plugin that
> gives your project logical nested modules based on its directory layout, as is
> common in the build systems of many other languages.
>
> So, src/server/foo.ml <http://foo.ml/> becomes Server.Foo, and src/client/foo.ml <http://foo.ml/> becomes
> Client.Foo. There is no conflict between the two foo.ml <http://foo.ml/> files, and thus no need
> to call them server_foo.ml <http://server_foo.ml/> and client_foo.ml <http://client_foo.ml/>.
>
> The project page and documentation can be found here:
>
> https://github.com/aantron/namespaces <https://github.com/aantron/namespaces>
>
> Namespaces works, but it abuses Ocamlbuild heavily, so there may be many corner
> cases that are not yet addressed well. Bug reports are very much welcome. If
> something can’t be fixed by changing Namespaces, perhaps Namespaces will be a
> good point of discussion for updating Ocamlbuild itself, or other OCaml tooling.
>
>
> Regards and enjoy,
> Anton
>
>
> P.S. How is Ocamlbuild spelled? I have seen it as Ocamlbuild, OCamlbuild (which
> stands to reason), and ocamlbuild in monospace font, in the original manual.
>
[-- Attachment #2: Type: text/html, Size: 4054 bytes --]
next prev parent reply other threads:[~2016-02-29 18:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 16:40 Anton Bachin
2016-02-29 16:53 ` Arto Bendiken
2016-02-29 18:37 ` Ivan Gotovchits
2016-02-29 18:45 ` Anton Bachin [this message]
2016-03-01 1:00 ` Junsong Li
2016-03-01 9:25 ` Thomas Refis
2016-03-07 22:38 ` Anton Bachin
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=4C6ACEE0-9F61-431D-8FD1-1FE88E5142FA@gmail.com \
--to=antronbachin@gmail.com \
--cc=caml-list@inria.fr \
--cc=ivg@ieee.org \
/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