From: Xavier Leroy <xavier.leroy@inria.fr>
To: Blair Zajac <blair@orcaware.com>
Cc: Alessandro Baretta <alex@baretta.com>, Ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Compiler killer code?
Date: Mon, 10 Jun 2002 17:25:47 +0200 [thread overview]
Message-ID: <20020610172547.A20522@pauillac.inria.fr> (raw)
In-Reply-To: <3D039993.BB852B4F@orcaware.com>; from blair@orcaware.com on Sun, Jun 09, 2002 at 11:08:19AM -0700
> I think this points to something that should be considered for
> future Ocaml development, that being a comprehensive test suite
> to check the language.
No one can object to this -- just like no one can object to "regular
exercice at the gym is good for you"; it's just that few have the
fortitute to actually do it. Developing a good test suite takes about
as much effort as writing the software being tested.
For OCaml, we have some test suites for a few specific libraries and
run-time facilities, but that's about it. Compilers and type-checkers
are even harder to test than run-time libraries.
So, if anyone wants to tackle this challenge, that would be very
useful indeed, but be aware that it's a huge task.
- Xavier Leroy
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2002-06-10 15:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-08 14:32 Alessandro Baretta
2002-06-08 14:34 ` William Lee Irwin III
2002-06-08 18:30 ` William Lovas
2002-06-09 13:29 ` Alessandro Baretta
2002-06-09 13:41 ` Xavier Leroy
2002-06-09 18:08 ` Blair Zajac
2002-06-10 10:57 ` [Caml-list] " Michal Moskal
2002-06-12 8:37 ` Xavier Leroy
2002-06-10 15:25 ` Xavier Leroy [this message]
2002-06-10 2:42 ` [Caml-list] " Jacques Garrigue
2002-06-10 7:47 ` Alessandro Baretta
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=20020610172547.A20522@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=alex@baretta.com \
--cc=blair@orcaware.com \
--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).