From: David Allsopp <dra-news@metastack.com>
To: "Daniel Bünzli" <daniel.buenzli@erratique.ch>,
"Adrien Nader" <adrien@notk.org>
Cc: Malcolm Matalka <mmatalka@gmail.com>,
"caml-list@inria.fr" <caml-list@inria.fr>
Subject: RE: [Caml-list] Suggested way to determine platform specific capabilities in build system?
Date: Sun, 19 Apr 2015 10:13:03 +0000 [thread overview]
Message-ID: <E51C5B015DBD1348A1D85763337FB6D9E9A8A570@Remus.metastack.local> (raw)
In-Reply-To: <67E83AEE021C4CF3826AA7A3575C5635@erratique.ch>
Daniel Bünzli wrote:
> Le dimanche, 19 avril 2015 à 08:47, Adrien Nader a écrit :
<snip>
> > The proper way to do it is to test for features instead. Want to know
> > if function foo is available in library bar? Well, just reference it
> > and see if compilation and/or linking fails.
>
> I know this is the way autocrap likes to work; it may seem smart but I
> think that's completely retarded.
Um, while your arguments often veer a little towards ad hominem attacks, the word "retarded" used in this context is extremely offensive, even if that is not what you intended (making allowance that while your English is extremely good, it is not your first language).
One of the many nice things about this email list is that the language used on it is generally civil!
I apologise if it turns out that I'm only person mildly offended...
David
next prev parent reply other threads:[~2015-04-19 10:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 10:51 Malcolm Matalka
2015-04-14 11:23 ` Daniel Bünzli
2015-04-14 13:17 ` Thomas Gazagnaire
2015-04-19 6:47 ` Adrien Nader
2015-04-19 8:38 ` Daniel Bünzli
2015-04-19 10:13 ` David Allsopp [this message]
2015-04-19 12:11 ` Daniel Bünzli
2015-04-19 19:14 ` Emmanuel Surleau
2015-04-20 9:55 ` Ben Millwood
2015-04-17 10:38 ` Ivan Gotovchits
2015-04-21 21:36 ` Richard W.M. Jones
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=E51C5B015DBD1348A1D85763337FB6D9E9A8A570@Remus.metastack.local \
--to=dra-news@metastack.com \
--cc=adrien@notk.org \
--cc=caml-list@inria.fr \
--cc=daniel.buenzli@erratique.ch \
--cc=mmatalka@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).