From owner-cvs-lib  Sat Nov 22 22:08:35 1997
Return-Path: <owner-cvs-lib>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id WAA21560
          for cvs-lib-outgoing; Sat, 22 Nov 1997 22:08:35 -0800 (PST)
          (envelope-from owner-cvs-lib)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA21328;
          Sat, 22 Nov 1997 22:03:19 -0800 (PST)
          (envelope-from bde@FreeBSD.org)
From: Bruce Evans <bde@FreeBSD.ORG>
Received: (from bde@localhost)
	by freefall.freebsd.org (8.8.6/8.8.5) id WAA07387;
	Sat, 22 Nov 1997 22:02:48 -0800 (PST)
Date: Sat, 22 Nov 1997 22:02:48 -0800 (PST)
Message-Id: <199711230602.WAA07387@freefall.freebsd.org>
To: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-lib@FreeBSD.ORG
Subject: cvs commit: src/lib/libc/stdio vfscanf.c
Sender: owner-cvs-lib@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

bde         1997/11/22 22:02:48 PST

  Modified files:
    lib/libc/stdio       vfscanf.c 
  Log:
  Fixed long double formats.  They were mostly not implemented except
  on systems where long doubles are just doubles.  FreeBSD hasn't
  been such a system since it started using gcc-2.5 many years ago.
  The fix is of low quality.  It loses precision.
  
  scanf() of long doubles doesn't seem to be used much, but gdb-4.16
  uses %Lg format in its expression parser if it thinks that the
  system supports printf'ing of long doubles.  The symptom was that
  floating point literals were usually interpreted to be 0.0.
  
  Revision  Changes    Path
  1.12      +7 -4      src/lib/libc/stdio/vfscanf.c