caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: David Allsopp <dra-news@metastack.com>
To: "moosotc@gmail.com" <moosotc@gmail.com>,
	"caml-list@inria.fr" <caml-list@inria.fr>
Subject: RE: [Caml-list] 4.03.0+beta2
Date: Fri, 1 Apr 2016 15:23:41 +0000	[thread overview]
Message-ID: <E51C5B015DBD1348A1D85763337FB6D9EA3E0016@Remus.metastack.local> (raw)
In-Reply-To: <878u0xtlha.fsf@gmail.com>

moosotc@gmail.com wrote:
> Damien Doligez <damien.doligez@inria.fr> writes:
> > Dear OCaml users,
> >
> > OCaml release 4.03.0 will arrive in about 2 weeks.  We have created a
> > second beta version for your testing pleasure.  Please test your
> > favourite software with it and let me know whether it works for you.
> >
> > If you are a library author, please make sure your library will work
> > with 4.03.0, and update it if needed.
> >
> > This beta version is available as an OPAM switch (4.03.0+beta2) and
> > also as source code at this address:
> >   http://caml.inria.fr/pub/distrib/ocaml-4.03/
> >
> > Happy hacking,
> >
> 
> Some of my code is normally built with -warn-error +a -w +a,

By normally, you do mean "in development-mode only", right...

On 01 December 2010 at 14:29, Damien Doligez wrote:
> 
> On 2010-11-27, at 11:21, David Allsopp wrote:
> 
> > and set Warning 28 to be on by default for [Foo _] - that would simply 
> > mean that 3.11/3.12 code using that syntax would emit warnings in "3.13"
> > rather than actually breaking (unless you've including -warn-error - but
> > that's always seemed to me to be a development option, not a release 
> > option...)
>
>
> Hear, hear!  This is in fact very important and bears repeating:
> don't use -warn-error in released code.

moosotc@gmail.com continued:
> but with
> 4.03 the compilation fails due to deprecated Char.lowercase. Alternative
> (lowercase_ascii) is not available on <4.03 and I'd like to avoid +a-3 if
> I can help it.

What's wrong with either pre-processing or selecting an alternative file in your configure step? Various examples of both in findlib (which contains a compatibility package for the Bytes module) and batteries (which contains easily-adaptable compatibility shims for missing constructors and features in the Unix module)


David

  reply	other threads:[~2016-04-01 15:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-01 14:01 Damien Doligez
2016-04-01 15:08 ` moosotc
2016-04-01 15:23   ` David Allsopp [this message]
2016-04-01 15:31     ` moosotc
2016-04-02 11:52 ` Goswin von Brederlow
2016-04-02 18:15   ` Fabrice Le Fessant
2016-04-04  8:00   ` François Bobot

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=E51C5B015DBD1348A1D85763337FB6D9EA3E0016@Remus.metastack.local \
    --to=dra-news@metastack.com \
    --cc=caml-list@inria.fr \
    --cc=moosotc@gmail.com \
    /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).