summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorManuel Novoa III <mjn3@codepoet.org>2003-09-22 05:43:44 +0000
committerManuel Novoa III <mjn3@codepoet.org>2003-09-22 05:43:44 +0000
commitf9243338185186b9fd9cb8c34c6b53899b17cdec (patch)
treef304f013aec03be5523e4a39463f261da7d7a86b /docs
parent84c79075fa2465e9d46ccae12f16e523c5c24e4b (diff)
One more scanf difference.
Diffstat (limited to 'docs')
-rw-r--r--docs/Glibc_vs_uClibc_Differences.txt4
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/Glibc_vs_uClibc_Differences.txt b/docs/Glibc_vs_uClibc_Differences.txt
index 63b0aaaaf..9d29267e2 100644
--- a/docs/Glibc_vs_uClibc_Differences.txt
+++ b/docs/Glibc_vs_uClibc_Differences.txt
@@ -140,6 +140,10 @@ stdio
9) The FILEs created by glibc's fmemopen(), open_memstream(), and fopencookie()
are not capable of wide orientation. The corresponding uClibc routines do
not have this limitation.
+10) For scanf, the C99 standard states "The fscanf function returns the value of
+ the macro EOF if an input failure occurs before any conversion." But glibc's
+ scanf does not respect conversions for which assignment was surpressed, even
+ though the standard states that the value is converted but not stored.
glibc bugs that Ulrich Drepper has refused to acknowledge or comment on
( http://sources.redhat.com/ml/libc-alpha/2003-09/ )