Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Jean-Christophe Filliatre <filliatr@csl.sri.com>
To: Amit Dubey <adubey@hopper.math.uwaterloo.ca>
Cc: caml-list@inria.fr
Subject: Re: Suggestion: Print more error messages?
Date: Fri, 12 May 2000 10:30:40 -0700 (PDT)	[thread overview]
Message-ID: <14620.16320.749238.299042@cylinder.csl.sri.com> (raw)
In-Reply-To: <200005121701.NAA03522@hopper.math.uwaterloo.ca>


> 	I have a short question about error messages.  I've notived that
> ocamlc will often quit after detecting the first error.  I find it much
> more useful to get a number of errors (at least 3-6), even if some of
> them may be spurious.  Is it possible to implement such behaviour?

You don't really need such a feature, since the ocaml compiler is very
fast. Thus,  you can "recompile" and "next-error"  very often, without
wasting time waiting for the compiler (With slow compilers, like JDK's
java compiler, you really need such a feature!) And thanks to the true
separate compilation of ocaml's  modules, you only recompile few files
each time. 

I agree that ocaml's native-code compiler may be quite slow sometimes,
but due to the consistency between the two compilers, you can developp
with the  bytecode compiler,  which is really  fast, and then  turn to
native-code when you are done with the development-phase and start the
test-phase.

However, I guess that there are also difficulties in finding more than
one error in a strongly typed language...

-- 
Jean-Christophe Filliatre    
  Computer Science Laboratory   Phone (650) 859-5173
  SRI International             FAX   (650) 859-2844
  333 Ravenswood Ave.           email  filliatr@csl.sri.com
  Menlo Park, CA 94025, USA     web    http://www.csl.sri.com/~filliatr

  



  reply	other threads:[~2000-05-13  9:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-12 17:01 Amit Dubey
2000-05-12 17:30 ` Jean-Christophe Filliatre [this message]
2000-05-14 14:45   ` John Max 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=14620.16320.749238.299042@cylinder.csl.sri.com \
    --to=filliatr@csl.sri.com \
    --cc=adubey@hopper.math.uwaterloo.ca \
    --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