From: Florent Ouchet <florent.ouchet@imag.fr>
To: "Hezekiah M. Carty" <hcarty@atmos.umd.edu>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml 3.12.0+beta1
Date: Fri, 25 Jun 2010 00:05:44 +0200 [thread overview]
Message-ID: <20100625000544.142418fa5cp6ye9k@webmail.imag.fr> (raw)
In-Reply-To: <AANLkTin4WhT942SwtKsODH07t-WF4P0hR4njvcg8WG4Y@mail.gmail.com>
"Hezekiah M. Carty" <hcarty@atmos.umd.edu> a écrit :
> The trailing _ in a record match is not required. It is allowed in
> 3.12, and in combination with an optional warning flag it can be used
> to check for incomplete record matches. Why is any preprocessing
> needed? If an application is written to require OCaml 3.12.x or
> later, why would you expect it to compile with an earlier version?
Software development is not your perfect and ideal world. Would you
buy a brand new car because your current two-month-old car does not
have seat belt reminders? New warnings are almost the only
improvements I'm interested in 3.12.
Sometimes you have to support old compiler versions (this choice is
not yours) and you need a complete confidence in all the thousands
record pattern matchings of your application, some of them (maybe 30%)
are intentionally left incomplete in order to keep the code as simple
as possible.
Without preprocessing scripts, I will not be able to insert extra "_"
for masking intentionally-left-incomplete pattern matchings. The
compilation log will be polluted by hundred warnings (false-positive).
Finally, the catch of the few remaining should-not-be-incomplete
pattern matchings (true-positive) will be very hard.
Anyway, I'm running out of arguments and the problem is still there...
I would have wasted less time in having the scripts setup than in
arguing here.
--
Florent Ouchet
PhD Student, CIS/VDS Groups
TIMA Laboratory, Grenoble, France
next prev parent reply other threads:[~2010-06-24 22:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 13:07 Damien Doligez
2010-06-16 16:28 ` [Caml-list] " Yoann Padioleau
2010-06-16 18:40 ` Martin Jambon
2010-06-16 20:52 ` Török Edwin
2010-06-17 13:35 ` xclerc
2010-06-18 14:56 ` xclerc
2010-06-19 5:51 ` Stéphane Glondu
2010-06-24 9:38 ` Florent Ouchet
2010-06-24 17:45 ` Martin Jambon
2010-06-24 18:59 ` Florent.Ouchet
2010-06-24 19:29 ` Dmitry Bely
2010-06-24 19:31 ` Mathias Kende
2010-06-24 19:39 ` Till Varoquaux
2010-06-24 20:49 ` Florent Ouchet
2010-06-24 20:57 ` Hezekiah M. Carty
2010-06-24 22:05 ` Florent Ouchet [this message]
2010-06-25 5:54 ` bluestorm
2010-06-25 6:24 ` Florent Ouchet
2010-06-25 8:17 ` bluestorm
2010-06-25 8:48 ` David Allsopp
2010-06-25 9:35 ` bluestorm
2010-06-25 7:29 ` bluestorm
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=20100625000544.142418fa5cp6ye9k@webmail.imag.fr \
--to=florent.ouchet@imag.fr \
--cc=caml-list@inria.fr \
--cc=hcarty@atmos.umd.edu \
/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