From: Chet Murthy <murthy@pauillac.inria.fr>
To: Christophe Raffalli <cr@dcs.ed.ac.uk>
Cc: Judicael.Courant@lip.ens-lyon.fr, caml-list@margaux.inria.fr
Subject: Re: Irrelevant variables in patterns
Date: Sat, 28 May 1994 13:12:46 +0200 [thread overview]
Message-ID: <29741.770123566@pauillac.inria.fr> (raw)
In-Reply-To: Your message of Sat, 28 May 1994 12:08:22 -0000. <13661.9405281108@colonsay.dcs.ed.ac.uk>
>>>>> On Sat, 28 May 1994 12:08:22 -0000, Christophe Raffalli <cr@dcs.ed.ac.uk> said:
> Superfluous warning confuse the programmer, and cause him to
> disregard the warnings completely. Which can cause him real pain
> when it was a warning that he should have heeded.
CR> I strongly disagree with this statement. If you get a lot of
CR> warning, it means you have a particular style of programming
CR> (for instance catching all exceptions in most of the
CR> handler). Then what you really needs is a compiler option to
CR> discard a particular warning (or class or warning) so you only
CR> get the warnings which are relevant to you programming style.
How about an ML-Lint? Anybody out there writing one?
--chet--
next prev parent reply other threads:[~1994-05-30 9:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-05-26 13:03 Judicael Courant
1994-05-27 18:01 ` Christophe Raffalli
1994-05-28 10:16 ` Chet Murthy
1994-05-28 10:36 ` Christophe Raffalli
1994-05-28 10:43 ` Chet Murthy
1994-05-28 11:01 ` Christophe Raffalli
1994-05-28 11:05 ` Chet Murthy
1994-05-28 11:09 ` Christophe Raffalli
1994-05-28 11:08 ` Christophe Raffalli
1994-05-28 11:12 ` Chet Murthy [this message]
1994-05-30 14:49 ` John Harrison
1994-05-30 18:20 ` calla
1994-05-30 8:53 ` Xavier Leroy
1994-05-30 17:57 ` Christophe Raffalli
1994-05-27 18:58 Damien Doligez
1994-05-30 13:15 Judicael Courant
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=29741.770123566@pauillac.inria.fr \
--to=murthy@pauillac.inria.fr \
--cc=Judicael.Courant@lip.ens-lyon.fr \
--cc=caml-list@margaux.inria.fr \
--cc=cr@dcs.ed.ac.uk \
/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