caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Basile STARYNKEVITCH <basile@starynkevitch.net>
To: Romain Bardou <Romain.Bardou@lri.fr>
Cc: caml-list <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] Module abbreviation
Date: Fri, 18 Dec 2009 07:55:46 +0100	[thread overview]
Message-ID: <4B2B2772.7030803@starynkevitch.net> (raw)
In-Reply-To: <4B2A1784.2060008@lri.fr>

Romain Bardou wrote:
> Basile STARYNKEVITCH wrote:
>> Romain Bardou wrote:
>>> Hello, dear Caml-list,
>>>
>>> I have a file ast.mli. It has no .ml implementation as it contains only
>>> type definitions.
>>
>> Then you should name that file ast.ml. Last time I tested (more than a
>> year ago) n ast.ml file without corresponding ast.mli file is handled as
>> if ast.mli was the output of ocamlc -i ast.ml.
>>
>> Regards
> 
> Yes, this seems to be the easiest way. It's too bad that this implies
> having a .cmo to link against just for some type definitions, though.


Why is that bad?  The *.cm[oi] files are the only ones containing the processed type & module information, and we 
obviously don't want ocamlc to reparse ast.mli each time it is needed.

Regards

-- 
Basile STARYNKEVITCH         http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mines, sont seulement les miennes} ***


  reply	other threads:[~2009-12-18  6:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-15 16:39 Romain Bardou
2009-12-15 16:56 ` [Caml-list] " Ashish Agarwal
2009-12-15 23:28   ` David Allsopp
     [not found]   ` <-5655904566200171061@unknownmsgid>
2009-12-16  3:17     ` Ashish Agarwal
2009-12-15 17:01 ` Basile STARYNKEVITCH
2009-12-17 11:35   ` Romain Bardou
2009-12-18  6:55     ` Basile STARYNKEVITCH [this message]
2009-12-18 12:06       ` Romain Bardou

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=4B2B2772.7030803@starynkevitch.net \
    --to=basile@starynkevitch.net \
    --cc=Romain.Bardou@lri.fr \
    --cc=caml-list@yquem.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).