From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18053 invoked by alias); 28 Apr 2010 08:15:56 -0000 Received: (qmail 18015 invoked by uid 48); 28 Apr 2010 08:15:41 -0000 Date: Wed, 28 Apr 2010 08:15:00 -0000 Message-ID: <20100428081541.18014.qmail@sourceware.org> From: "zimmerma+gcc at loria dot fr" To: glibc-bugs@sources.redhat.com In-Reply-To: <20100407084013.11475.zimmerma+gcc@loria.fr> References: <20100407084013.11475.zimmerma+gcc@loria.fr> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug libc/11475] support for printing/reading decimal numbers (_Decimal64) X-Bugzilla-Reason: CC Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org X-SW-Source: 2010-04/txt/msg00165.txt.bz2 ------- Additional Comments From zimmerma+gcc at loria dot fr 2010-04-28 08:15 ------- (In reply to comment #6) > This is what the printf hooks are for. I'm not going to add any such > non-standard conversion. It far too dangerous a compability risk going forward. Dear Ulrich, please can you explain why this is "non-standard". With respect to which standard? Is _Decimal64 standard? Also, if someone provides changes to scanf/printf based on functions already existing in libbid or libdecnumber (currently used internally by gcc) for conversions between strings and decimal formats, would them be included in glibc? -- http://sourceware.org/bugzilla/show_bug.cgi?id=11475 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.