diff options
| author | Manuel Novoa III <mjn3@codepoet.org> | 2002-11-08 04:34:06 +0000 |
|---|---|---|
| committer | Manuel Novoa III <mjn3@codepoet.org> | 2002-11-08 04:34:06 +0000 |
| commit | c663924c3dd8f10ac2aff7d293f8d705aee979d2 (patch) | |
| tree | eb25dfc46670d5622465f6157b1fe34edf29ac81 | |
| parent | 5dcc4c2e25452b932e3c45bf25cfb89db461bba7 (diff) | |
Add notes about setvbuf and struct tm extension fields tm_gmtoff and tm_zone.
| -rw-r--r-- | docs/Glibc_vs_uClibc_Differences.txt | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/Glibc_vs_uClibc_Differences.txt b/docs/Glibc_vs_uClibc_Differences.txt index bade0e456..2a36be939 100644 --- a/docs/Glibc_vs_uClibc_Differences.txt +++ b/docs/Glibc_vs_uClibc_Differences.txt @@ -82,6 +82,9 @@ time functions echo CST6CDT > /etc/TZ 3) Currently, locale specific eras and alternate digits are not supported. They are on my TODO list. +4) The extension fields tm_gmtoff and tm_zone, even prefixed with "__", are + not currently supported as they aren't required by SUSv3 and I didn't + need them when I wrote the time code. wide char support ----------------- @@ -123,6 +126,9 @@ stdio 6) uClibc's scanf still needs work. 7) The functions fcloseall() and __fpending() can behave differently than their glibc counterparts. +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. More to follow as I think of it... |