From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/254 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Wishlist for musl 1.0 ? Date: Thu, 7 Apr 2011 22:41:26 -0400 Message-ID: <20110408024126.GX16304@brightrain.aerifal.cx> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1312595688 11293 80.91.229.12 (6 Aug 2011 01:54:48 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 6 Aug 2011 01:54:48 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: envelope-from@hidden Fri Apr 8 06:46:07 2011 Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:254 Archived-At: Greetings again, With most essential functionality implemented and serious bug-hunting underway, I hope to quickly move out of the "alpha" phase, and aim to release "1.0" sometime this summer. I have put together a tentative list of requirements for what will constitute "musl 1.0", on which I would like some feedback from the community. I'd like to go ahead and decide on these so the project can have some concrete goals and a way to measure how far we still have to go. Comments welcome! Regards, Rich Proposed requirements for 1.0: Implementations of all interfaces in ISO C99, including math. Implementations of all required functions in POSIX 2008 base and explicitly-supported option groups. Character class handling synchronized with latest Unicode. Dynamic linking and dynamic loader (dlopen/dlsym) support for both dynamic and static linked applications. Known compatibility with a yet-to-be-determined collection of applications selected as particularly important. Ability of the dynamic linker to successfully load and run glibc-linked programs as long as they don't use features which are not-yet-implemented in musl. Support for at least one C++ compiler and library, but not necessarily any ABI-compatibility with C++ programs which were not explicitly built against musl. Documenting of all implementation-defined behavior as required by the C and POSIX standards, as well as implementation details that might be of interest to programmers using musl such as the behavior of malloc, threads, stdio, etc. and how they compare to other implementations.