mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: Revised 1.0 wishlist
Date: Fri, 7 Dec 2012 23:17:07 -0500	[thread overview]
Message-ID: <20121208041707.GT20323@brightrain.aerifal.cx> (raw)
In-Reply-To: <20121204235937.GA23989@brightrain.aerifal.cx>

On Tue, Dec 04, 2012 at 06:59:37PM -0500, Rich Felker wrote:
> The following wishlist is a draft. I may have missed some items, and
> the compatibility goals and testing goals are new ideas subject to
> discussion.

One further goal I'd like to add is increasing the level of ABI
stability. If it seems feasible to match the C++ ABI with glibc, I
think we should go ahead and do that before 1.0 rather than after
(where we would break our own C++ ABI). That means using matching
struct tags for structures that might be involved as arguments in C++
functions, dealing with some types that are defined differently (like
glibc using long instead of a pointer type for pthread_t), etc. In
really ugly cases like pthread_t, I think we could put the bad
definition for compatibility under #ifdef __cplusplus so that C
programs get the benefits of musl's superior definition.

Thoughts on this? Anybody up for auditing the differences, either
fully or at least partially to see if aligning them is feasible? The
reason I'm interested in this is that I suspect a decent portion of
the binaryware apps/libs we might want to support may be written in
C++ rather than C.

Rich


  reply	other threads:[~2012-12-08  4:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-04 23:59 Rich Felker
2012-12-08  4:17 ` Rich Felker [this message]
2012-12-13 22:03 ` Status of 1.0 wishlist items? Rich Felker
2012-12-13 22:36   ` John Spencer
2012-12-13 23:48     ` Rich Felker
2012-12-14  0:41       ` Szabolcs Nagy
2012-12-21 20:22       ` John Spencer
2012-12-14  5:14   ` Luca Barbato
2012-12-17 12:47   ` ojab

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=20121208041707.GT20323@brightrain.aerifal.cx \
    --to=dalias@aerifal.cx \
    --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).