diff options
| author | Manuel Novoa III <mjn3@codepoet.org> | 2002-11-22 03:05:27 +0000 |
|---|---|---|
| committer | Manuel Novoa III <mjn3@codepoet.org> | 2002-11-22 03:05:27 +0000 |
| commit | c386ddb4d8a1b076d94ebe8b85ca5d0dd124892b (patch) | |
| tree | e30c9d77393721491f4a3a42e223980352b72ff8 /docs/Glibc_vs_uClibc_Differences.txt | |
| parent | 2b8a8dc7144328f301390f13fa560d29a410e34f (diff) | |
Ok... here's the summary:
Hopefully locale support will build when cross compiling now. Collation is
still not supported, but that's what I'm currently working on. In the
next couple of days, I'll probably put up a couple of files for download
that will save people the trouble of generating all the glibc locales.
Added *wprintf functions, although they currently don't support floating
point. That will be fixed when I rewrite _dtostr... or possibly before.
Added the wcsto{inttype} functions.
Added iconv() and a mini iconv utility. The require locale support and
only provide for conversions involving the various unicode encodings
{ UCS-4*, UCS-2*, UTF-32*, UTF-16*, UTF-8 }, the 8-bit codesets built
with the locale data, and the internal WCHAR_T.
Diffstat (limited to 'docs/Glibc_vs_uClibc_Differences.txt')
| -rw-r--r-- | docs/Glibc_vs_uClibc_Differences.txt | 8 |
1 files changed, 3 insertions, 5 deletions
diff --git a/docs/Glibc_vs_uClibc_Differences.txt b/docs/Glibc_vs_uClibc_Differences.txt index e0e1e6af4..8ebca10a9 100644 --- a/docs/Glibc_vs_uClibc_Differences.txt +++ b/docs/Glibc_vs_uClibc_Differences.txt @@ -100,17 +100,13 @@ wide char support representation of wchar's is assumed to be 31 bit unicode values in native endian representation. Also, the underlying char encoding is assumed to match ASCII in the range 0-0x7f. -2) In the C locale, uClibc's mb<->wc conversion functions map 0x80-CHAR_MAX - onto their wide/narrow equivalents. glibc's conversion functions treat - them as illegal. locale support -------------- 1) The target for support is SUSv3 locale functionality. While nl_langinfo has been extended, similar to glibc, it only returns values for related locale entries. -2) The locale code is not cross-compiler friendly. This should be fixed soon. -3) Currently, collation support is being implemented. +2) Currently, collation support is being implemented. stdio ----- @@ -136,6 +132,8 @@ stdio 8) uClibc's setvbuf is more restrictive about when it can be called than glibc's is. The standards specify that setvbuf must occur before any other operations take place on the stream. +9) Right now, %m is not handled properly by printf when the format uses positional + args. More to follow as I think of it... |