PRB: gcvt() Generates Exponential Notation for 0.0x

 Last reviewed: July 24, 1997
Article ID: Q37794

The information in this article applies to:
  • The C Run-time (CRT) included with: - Microsoft C for MS-DOS, versions 5.1, 6.0, 6.0a, 6.0ax - Microsoft C for OS/2, versions 5.1, 6.0, 6.0a - Microsoft C/C++ for MS-DOS, version 7.0 - Microsoft Visual C++ for Windows, versions 1.0, 1.5 - Microsoft Visual C++ 32-bit Edition, versions 1.0, 2.0, 4.0, 5.0

SYMPTOMS

The gcvt() function returns a value in scientific notation, without regard to the specified precision, when the floating-point value has the form "0.0<x>" and <x> is any sequence of digits.

CAUSE

This is expected behavior for gcvt().

RESOLUTION

If this behavior is not desired, use the fcvt() function to convert the floating-point number to a string.

MORE INFORMATION

The following code demonstrates this behavior:

Sample Code

   /*
    * Compile options needed: None
    */

   #include <stdio.h>
   #include <stdlib.h>

   char buffer[50];
   int precision = 20;

   void main(void)
   {
      gcvt(-0.1123, precision, buffer);    /* Decimal output */
      printf("buffer ........\"%s\"\n", buffer);

      gcvt(-0.0123, precision, buffer);    /* Scientific notation */
      printf("buffer ........\"%s\"\n", buffer);
   }

Keywords : CRTIss kbfasttip
Version : 5.1 6.0 6.0a 6.0ax 7.0 1.0 1.5 2
Platform : MS-DOS NT OS/2 WINDOWS
Issue type : kbprb

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: July 24, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.