[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120713181254.GA31206@brightrain.aerifal.cx>
Date: Fri, 13 Jul 2012 14:12:54 -0400
From: Rich Felker <dalias@...ifal.cx>
To: musl@...ts.openwall.com
Subject: Draft: musl promo materials
Hi all,
Here's a quick draft (and request for input/suggestions) of
points/highlights about musl to eventually be incorporated into the
website and other opportunities to promote musl. With
embedded-relevant ports getting integrated now, I'm thinking this sort
of thing will also be useful for sending announcements to relevant
mailing lists, etc. Anything big I'm missing?
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.
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.
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.
