caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Dawid Toton <d0@wp.pl>
To: caml-list@inria.fr
Subject: [Caml-list] Re: Preferred layout for new packages
Date: Thu, 15 Nov 2012 10:59:38 +0100	[thread overview]
Message-ID: <50A4BD0A.9040804@wp.pl> (raw)
In-Reply-To: <20121115092037.GC26744@securactive.lan>

On 11/15/2012 10:20 AM, rixed@happyleptic.org wrote:
> -[ Thu, Nov 15, 2012 at 12:13:58AM -0800, vincent.hugot@gmail.com ]----
>> I for one like the (short-)tests-as-comments approach: being near the
>> function, they serve as short specifications, and being comments, they don't
>> alter the compilation process in the least.
>
> The only drawback I saw is that adding or modifying a test triggers the
> recompilation of the whole unit when using makefiles (since the file changed).
> I wonder if there exist a tool that's able to find out that since only comments
> where changed the module need not be recompiled. Maybe omake can do this ?
>

You usually want correct line numbers to be preserved in the executable 
for e.g. assertion failures. So, in general, it's not possible to save 
time in the way you describe unless the compiler itself works in an 
incremental manner.
Dawid


  reply	other threads:[~2012-11-15  9:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.38rAsBvHd+quECbtcbTH9HW+J6U@ifi.uio.no>
     [not found] ` <fa.YCrkHurCi6yY5s0Qg1r6uLWNQdY@ifi.uio.no>
     [not found]   ` <fa.oeqp0ymFFL+o76ut/LjBeQhUcjQ@ifi.uio.no>
     [not found]     ` <fa.pEDV80ILnW8x1YQyKuF3NBsK3Kw@ifi.uio.no>
     [not found]       ` <fa.LQofvqHUt8xj1kM1rvmQZF+Z7rw@ifi.uio.no>
2012-11-15  8:13         ` [Caml-list] " vincent.hugot
2012-11-15  8:31           ` Francois Berenger
2012-11-15  9:20           ` rixed
2012-11-15  9:59             ` Dawid Toton [this message]
2012-11-15 16:09               ` [Caml-list] " rixed
2012-11-15 17:22             ` [Caml-list] " Aleksey Nogin

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=50A4BD0A.9040804@wp.pl \
    --to=d0@wp.pl \
    --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).