From: Luc Maranget <luc.maranget@inria.fr>
To: alex@baretta.com (Alessandro Baretta)
Cc: caml-list@inria.fr (Ocaml)
Subject: Re: [Caml-list] Possible bug in module and class?
Date: Mon, 21 Oct 2002 14:32:54 +0200 (MET DST) [thread overview]
Message-ID: <200210211232.OAA0000007363@beaune.inria.fr> (raw)
In-Reply-To: <3DB3F02B.6070401@baretta.com> from "Alessandro Baretta" at oct 21, 2002 02:16:43
>
>
>
> I'm using O'Caml in an industrial project. Of course, I'd
> like to make sure that I give my customers the most stable
> environment possible. As more and more bugs are found and
> fixed in the CVS version, the temptation to upgrade from the
> official distribution becomes stronger. But is the CVS
> version usually more or less buggy than the official distro?
No one can tell, but an important point is that the CVS version is
unstable by nature.
>
> I know this is a very diffucult question, and that it is
> much easier to answer, "Try and it, and if you find a bug,
> report it." Yet, I would like the developers to take a stand
> on the use of the cvs source. Do you encourage widespread
> use? Do you encourage use only for testing purposes?
By using the CVS version you help the developpers, not your product.
If I were you, I would be selfish!
Of course in the long run helping Caml is helping yourself, but I
assume you are coding for food and that you eat every day.
>
> I ask because I would like to stick with official
> reccomendations, rather than experimenting on completely
> unknown grounds.
>
I am no industrial.
But for hevea I stick to the following guidelines.
- Always develop with the current distributed version.
- Avoid new features as much as possible.
- I check hevea at every compiler release.
- I case of bug I favor work-arounds in my code over enforcing upgrade (at
least until the next official Ocaml release).
I do not think my statement can be considered ``official'', just
common sense.
> TIA
>
> Alex
--Luc
-------------------
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-10-21 12:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 20:16 Bow-Yaw Wang
2002-10-21 6:26 ` Jacques Garrigue
2002-10-21 12:16 ` Alessandro Baretta
2002-10-21 12:32 ` Luc Maranget [this message]
2002-10-21 12:51 ` Alessandro Baretta
2002-10-22 2:16 ` Jacques Garrigue
2002-10-22 4:35 ` [Caml-list] Camlp4 pretty print comments Quetzalcoatl Bradley
2002-10-22 11:15 ` Daniel de Rauglaudre
2002-10-22 12:40 ` Sven Luther
2002-10-22 13:18 ` Stefano Zacchiroli
2002-10-22 13:44 ` Maxence Guesdon
2002-10-22 14:21 ` Daniel de Rauglaudre
2002-10-21 21:00 ` [Caml-list] Possible bug in module and class? Bow-Yaw Wang
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=200210211232.OAA0000007363@beaune.inria.fr \
--to=luc.maranget@inria.fr \
--cc=alex@baretta.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).