From f9243338185186b9fd9cb8c34c6b53899b17cdec Mon Sep 17 00:00:00 2001 From: Manuel Novoa III Date: Mon, 22 Sep 2003 05:43:44 +0000 Subject: One more scanf difference. --- docs/Glibc_vs_uClibc_Differences.txt | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'docs/Glibc_vs_uClibc_Differences.txt') 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/ ) -- cgit v1.2.3