mailing list of musl libc
 help / color / mirror / code / Atom feed
From: u-wsnj@aetey.se
To: musl@lists.openwall.com
Subject: Re: MUSL Feature Detection
Date: Thu, 5 Mar 2015 09:58:23 +0100	[thread overview]
Message-ID: <20150305085823.GX1264@example.net> (raw)
In-Reply-To: <20150305083315.GW1264@example.net>

On Thu, Mar 05, 2015 at 09:33:15AM +0100, u-wsnj@aetey.se wrote:
> On Wed, Mar 04, 2015 at 12:54:58PM -0800, William Ahern wrote:
> > So, is there any sort of sanctioned way to detect MUSL at all, version or no
> > version? Is there any interest in supporting any kind of feature detection,
> > such as an API that communicates implementation choices wrt unspecified and
> > undefined behavior.

Sorry for having made a too large citation.

To be clear, I commented only on the part:

> > So, is there any sort of sanctioned way to detect MUSL at all, version or no
> > version?

[skipping my former message]

As for your proposal

> > Is there any interest in supporting any kind of feature detection,
> > such as an API that communicates implementation choices wrt unspecified and
> > undefined behavior.

I did not mean to comment on this in the previous message.

It looks otherwise reasonable but amounts to a standardization effort
for a new API with exactly the details intentionally omitted by
the existing standards. This might be hard to accomplish.

Rune



  reply	other threads:[~2015-03-05  8:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04 20:54 William Ahern
2015-03-05  4:23 ` Rich Felker
2015-03-05  8:33 ` u-wsnj
2015-03-05  8:58   ` u-wsnj [this message]
2015-03-05 15:34     ` stephen Turner
2015-03-05 21:02       ` William Ahern
2015-03-05 21:38         ` Rich Felker

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=20150305085823.GX1264@example.net \
    --to=u-wsnj@aetey.se \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).