[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120713233052.GA1110@brightrain.aerifal.cx>
Date: Fri, 13 Jul 2012 19:30:52 -0400
From: Rich Felker <dalias@...ifal.cx>
To: musl@...ts.openwall.com
Subject: Re: Draft: musl promo materials
Updated version based on some comments.. I think the list is getting
long enough that it would possibly make sense to reorder/trim it for
the intended target audience in some usages, and only include the full
thing on the website.
Rich
----------------------------------------------------------------------
Consistent quality and implementation behavior from tiny embedded
systems to full servers.
Minimal machine-specific code, meaning less chance of breakage on
minority architectures and better success with "write once run
everywhere" development.
Extremely-efficient static and dynamic linking support, yielding small
binaries and minimal startup overhead.
Realtime-quality robustness. No unnecessary dynamic allocation. No
unrecoverable late failures. No lazy binding or lazy allocation.
MIT license.
Full math library with a focus on correctness. Exact and
correctly-rounded conversion between binary floating point and decimal
strings.
Reentrancy, thread-safety, and async-signal safety well beyond the
requirements of POSIX. Even snprintf and dprintf are fully reentrant
and async-signal-safe.
Highly resource-efficient POSIX threads implementation, making
multi-threaded application design viable even for memory-constrained
systems.
Simple source code and source tree layout, so it's easy to customize
or track down the cause of unexpected behavior or bugs, or simply
learn how the library works.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
