m4-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Changes to m4/doc/m4.texinfo,v


From: Eric Blake
Subject: Changes to m4/doc/m4.texinfo,v
Date: Wed, 07 Mar 2007 15:31:20 +0000

CVSROOT:        /sources/m4
Module name:    m4
Changes by:     Eric Blake <ericb>      07/03/07 15:31:14

Index: doc/m4.texinfo
===================================================================
RCS file: /sources/m4/m4/doc/m4.texinfo,v
retrieving revision 1.101
retrieving revision 1.102
diff -u -b -r1.101 -r1.102
--- doc/m4.texinfo      3 Mar 2007 21:10:24 -0000       1.101
+++ doc/m4.texinfo      7 Mar 2007 15:31:14 -0000       1.102
@@ -66,9 +66,9 @@
 @title GNU M4, version @value{VERSION}
 @subtitle A powerful macro processor
 @subtitle Edition @value{EDITION}, @value{UPDATED}
address@hidden by Ren@'e Seindal
address@hidden and Gary V. Vaughan
address@hidden and Eric Blake
address@hidden by Ren@'e Seindal, Fran@,{c}ois Pinard,
address@hidden Gary V. Vaughan, and Eric Blake
address@hidden (@email{bug-m4@@gnu.org})
 
 @page
 @vskip 0pt plus 1filll
@@ -431,11 +431,11 @@
 say what you expected to occur; this will help us decide whether the
 problem was really in the documentation.
 
-Once you've got a precise problem, send e-mail to (Internet)
+Once you've got a precise problem, send e-mail to
 @email{bug-m4@@gnu.org}.  Please include the version number of @code{m4}
 you are using.  You can get this information with the command
address@hidden --version}.  You can also run @kbd{make check} to generate the 
file
address@hidden/@/testsuite.log}, useful for including in your report.
address@hidden --version}.  You can also run @kbd{make check} to generate the
+file @file{tests/@/testsuite.log}, useful for including in your report.
 
 Non-bug suggestions are always welcome as well.  If you have questions
 about things that are unclear in the documentation or are just obscure
@@ -5996,6 +5996,10 @@
 @result{}56790
 len(format(`%-*X', `5000', `1'))
 @result{}5000
+ifelse(format(`%.1A', `1.999'), `0X1.0P+1', `success',
+       format(`%.1A', `1.999'), `0X2.0P+0', `success',
+       `fail')
address@hidden
 @end example
 
 Using the @code{forloop} macro defined earlier (@pxref{Forloop}), this
@@ -6022,13 +6026,15 @@
 @end example
 
 The builtin @code{format} is modeled after the ANSI C @samp{printf}
-function, and supports these @samp{%} specifiers: @samp{c},
address@hidden, @samp{d}, @samp{o}, @samp{x}, @samp{X}, @samp{u}, @samp{e},
address@hidden, @samp{f}, @samp{F}, @samp{g}, @samp{G}, and @samp{%}; it
-supports field widths and precisions, and the
-modifiers @samp{+}, @samp{-}, @address@hidden }}, @samp{0}, @samp{#}, @samp{h} 
and
+function, and supports these @samp{%} specifiers: @samp{c}, @samp{s},
address@hidden, @samp{o}, @samp{x}, @samp{X}, @samp{u}, @samp{a}, @samp{A},
address@hidden, @samp{E}, @samp{f}, @samp{F}, @samp{g}, @samp{G}, and
address@hidden; it supports field widths and precisions, and the modifiers
address@hidden, @samp{-}, @address@hidden }}, @samp{0}, @samp{#}, @samp{h} and
 @samp{l}.  For more details on the functioning of @code{printf}, see the
-C Library Manual.
+C Library Manual, or the @acronym{POSIX} specification (for example,
address@hidden is supported even on platforms that haven't yet implemented
+C99 hexadecimal floating point output natively).
 
 @c FIXME - format still needs some improvements.
 For now, unrecognized specifiers are silently ignored, but it is




reply via email to

[Prev in Thread] Current Thread [Next in Thread]