Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Brian Hurt <bhurt@janestcapital.com>
To: Florian Hars <hars@bik-gmbh.de>
Cc: OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Teaching bottomline, part 3: what should improve.
Date: Wed, 23 May 2007 11:11:09 -0400	[thread overview]
Message-ID: <4654598D.3010200@janestcapital.com> (raw)
In-Reply-To: <465455B7.50106@bik-gmbh.de>

[-- Attachment #1: Type: text/plain, Size: 899 bytes --]

Florian Hars wrote:

>Brian Hurt schrieb:
>  
>
>>Hundreds of lines?  I've seen ten's of lines, but never hundreds.
>>    
>>
>
>Not only hundreds of lines, but usually in a completely different file, too.
>
>This expression has type exactly_what_it_should be, but is here used with
>type compeletly_off_the_mark.
>
>How I hate it.
>
>  
>

.mli files.  Use them.  Trust me.

Simply because code compiles doesn't necessarily mean it's right.  Often 
times I write the .mli file first, as it's a convient level to think 
about what the interface to a module should be.  But at the very least 
you should use ocamlc -i to generate the .mli file when you are more or 
less done with the module, and then hand verify it as correct.  And then 
keep it around, to make sure the module remains correct in the face of 
future changes.  Doing this will keep type errors in the same file, at 
least.

Brian



[-- Attachment #2: Type: text/html, Size: 1360 bytes --]

  reply	other threads:[~2007-05-23 15:11 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-22 22:10 David Teller
2007-05-22 22:22 ` [Caml-list] " William D. Neumann
2007-05-23 13:07   ` David Teller
2007-05-22 22:26 ` Erik de Castro Lopo
2007-05-22 23:16 ` skaller
2007-05-23  2:46   ` David Thomas
2007-05-23  9:19   ` Vincent Hanquez
2007-05-23 12:49     ` Brian Hurt
2007-05-23 13:36       ` Gerd Stolpmann
2007-05-23 14:06         ` skaller
2007-05-23 14:54       ` Florian Hars
2007-05-23 15:11         ` Brian Hurt [this message]
2007-05-23 21:48       ` Vincent Hanquez
2007-05-24  8:04         ` Markus E.L.
2007-05-24  8:32           ` Vincent Hanquez
2007-05-24  9:51             ` skaller
2007-05-24 11:22               ` Vincent Hanquez
2007-05-23 13:55   ` David Teller
2007-05-22 23:19 ` skaller
2007-05-23 10:41   ` Richard Jones
2007-05-23 13:04     ` David Teller
2007-05-24 13:51       ` Richard Jones
2007-05-24 14:00         ` Robert Fischer
2007-05-24 14:00       ` Jon Harrop
2007-05-24 14:20         ` Robert Fischer
2007-05-24 14:34         ` David Teller
2007-05-24 14:21       ` skaller
2007-05-22 23:39 ` Jon Harrop
2007-05-23 18:54   ` Richard Jones
2007-05-23 19:27     ` Robert C Fischer
2007-05-23 19:34       ` Brian Hurt
2007-05-23 19:54         ` Robert Fischer
2007-05-23 21:46       ` Jon Harrop
2007-05-23 22:14         ` Jacques Garrigue
2007-05-24  1:38           ` Revolution Jon Harrop
2007-05-24  2:40             ` [Caml-list] Revolution skaller
2007-05-24  3:21             ` Chris King
2007-05-24 14:24               ` David Teller
2007-05-24 13:40         ` [Caml-list] Teaching bottomline, part 3: what should improve Brian Hurt
2007-05-23 19:29     ` Jon Harrop
2007-05-23 20:20   ` David Teller
2007-05-24 14:18     ` Jon Harrop
2007-05-24 14:23     ` skaller

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=4654598D.3010200@janestcapital.com \
    --to=bhurt@janestcapital.com \
    --cc=caml-list@inria.fr \
    --cc=hars@bik-gmbh.de \
    /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