From: Olaf Hering <olaf@aepfle.de>
To: caml-list@inria.fr
Subject: [Caml-list] removal of C compiler variables in in 4.06
Date: Tue, 18 Jul 2017 11:02:58 +0200 [thread overview]
Message-ID: <20170718090258.GB2151@aepfle.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 389 bytes --]
While wresting with labltk and 4.05 I noticed an backwards incompatible
change in labltk.git (986e116 "Fix for ocaml 4.06") and in ocaml.git
(cc7ad5650a "Get rid of BYTECC and NATIVECC"). What is the rationale to
break external users of BYTECC/NATIVECC? Perhaps labltk shouldnt have
used these variables in the first place. But if their usage is legitime,
why the needless breakage?
Olaf
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next reply other threads:[~2017-07-18 9:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 9:02 Olaf Hering [this message]
2017-07-18 9:23 ` Adrien Nader
2017-07-18 13:31 ` Olaf Hering
2017-07-18 11:37 ` Stéphane Glondu
2017-07-18 12:24 ` Gabriel Scherer
2017-07-18 12:59 ` Stéphane Glondu
2017-07-18 13:41 ` Olaf Hering
2017-07-18 13:49 ` Gabriel Scherer
2017-07-18 18:04 ` Olaf Hering
2017-07-18 13:28 ` Jesper Louis Andersen
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=20170718090258.GB2151@aepfle.de \
--to=olaf@aepfle.de \
--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).