This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[PATCH] more use of @dots{} in texinfo files
- From: Art Haas <ahaas at neosoft dot com>
- To: gcc-patches at gcc dot gnu dot org
- Date: Sat, 22 Jun 2002 14:34:52 -0500
- Subject: [PATCH] more use of @dots{} in texinfo files
Hi.
Here's a small patch that replaces "..." with the
texinfo command @dots{}. I did a "make info" successfully
after fiddling with the files. The patch is against the
gcc-3_1-branch info files.
My thanks to everyone contributing to GCC!
Art Haas
Index: c-tree.texi
===================================================================
RCS file: /cvsroot/gcc/gcc/gcc/doc/c-tree.texi,v
retrieving revision 1.31.2.1
diff -u -r1.31.2.1 c-tree.texi
--- c-tree.texi 25 Apr 2002 09:34:52 -0000 1.31.2.1
+++ c-tree.texi 22 Jun 2002 19:29:13 -0000
@@ -1453,7 +1453,7 @@
statement is a range of case labels. Such statements originate with the
extension that allows users to write things of the form:
@example
-case 2 ... 5:
+case 2 @dots{} 5:
@end example
The first value will be @code{CASE_LOW}, while the second will be
@code{CASE_HIGH}.
Index: extend.texi
===================================================================
RCS file: /cvsroot/gcc/gcc/gcc/doc/extend.texi,v
retrieving revision 1.64.2.2
diff -u -r1.64.2.2 extend.texi
--- extend.texi 11 Apr 2002 21:36:04 -0000 1.64.2.2
+++ extend.texi 22 Jun 2002 19:29:45 -0000
@@ -404,7 +404,7 @@
or arrays as values.
* Designated Inits:: Labeling elements of initializers.
* Cast to Union:: Casting to union type from any member of the union.
-* Case Ranges:: `case 1 ... 9' and such.
+* Case Ranges:: `case 1 @dots{} 9' and such.
* Mixed Declarations:: Mixing declarations and code.
* Function Attributes:: Declaring that functions have no side effects,
or that they can never return.
@@ -1397,7 +1397,7 @@
example:
@example
-#define debug(format, ...) fprintf (stderr, format, __VA_ARGS__)
+#define debug(format, @dots{}) fprintf (stderr, format, __VA_ARGS__)
@end example
Here @samp{@dots{}} is a @dfn{variable argument}. In the invocation of
@@ -1411,7 +1411,7 @@
argument. Here is an example:
@example
-#define debug(format, args...) fprintf (stderr, format, args)
+#define debug(format, args@dots{}) fprintf (stderr, format, args)
@end example
This is in all ways equivalent to the ISO C example above, but arguably
@@ -1438,7 +1438,7 @@
used with the token paste operator, @samp{##}. If instead you write
@example
-#define debug(format, ...) fprintf (stderr, format, ## __VA_ARGS__)
+#define debug(format, @dots{}) fprintf (stderr, format, ## __VA_ARGS__)
@end example
and if the variable arguments are omitted or empty, the @samp{##}
@@ -1654,11 +1654,11 @@
value, with no @samp{=}.
To initialize a range of elements to the same value, write
-@samp{[@var{first} ... @var{last}] = @var{value}}. This is a GNU
+@samp{[@var{first} @dots{} @var{last}] = @var{value}}. This is a GNU
extension. For example,
@example
-int widths[] = @{ [0 ... 9] = 1, [10 ... 99] = 2, [100] = 3 @};
+int widths[] = @{ [0 @dots{} 9] = 1, [10 @dots{} 99] = 2, [100] = 3 @};
@end example
@noindent
@@ -1768,7 +1768,7 @@
like this:
@example
-case @var{low} ... @var{high}:
+case @var{low} @dots{} @var{high}:
@end example
@noindent
@@ -1778,22 +1778,22 @@
This feature is especially useful for ranges of ASCII character codes:
@example
-case 'A' ... 'Z':
+case 'A' @dots{} 'Z':
@end example
-@strong{Be careful:} Write spaces around the @code{...}, for otherwise
+@strong{Be careful:} Write spaces around the @code{@dots{}}, for otherwise
it may be parsed wrong when you use it with integer values. For example,
write this:
@example
-case 1 ... 5:
+case 1 @dots{} 5:
@end example
@noindent
rather than this:
@example
-case 1...5:
+case 1@dots{}5:
@end example
@node Cast to Union
@@ -2016,7 +2016,7 @@
@smallexample
extern int
-my_printf (void *my_object, const char *my_format, ...)
+my_printf (void *my_object, const char *my_format, @dots{})
__attribute__ ((format (printf, 2, 3)));
@end smallexample
@@ -2543,7 +2543,7 @@
@smallexample
__attribute__((noreturn)) void d0 (void),
- __attribute__((format(printf, 1, 2))) d1 (const char *, ...),
+ __attribute__((format(printf, 1, 2))) d1 (const char *, @dots{}),
d2 (void)
@end smallexample
@@ -4109,7 +4109,7 @@
@smallexample
extern "C" @{
-extern int printf (char *, ...);
+extern int printf (char *, @dots{});
@}
class a @{
@@ -4549,7 +4549,7 @@
@smallexample
static const int table[] = @{
__builtin_constant_p (EXPRESSION) ? (EXPRESSION) : -1,
- /* ... */
+ /* @dots{} */
@};
@end smallexample
@@ -4597,7 +4597,7 @@
when testing pointer or floating-point values.
@end deftypefn
-@deftypefn {Built-in Function} void __builtin_prefetch (const void *@var{addr}, ...)
+@deftypefn {Built-in Function} void __builtin_prefetch (const void *@var{addr}, @dots{})
This function is used to minimize cache-miss latency by moving data into
a cache before it is accessed.
You can insert calls to @code{__builtin_prefetch} into code for which
@@ -4625,7 +4625,7 @@
a[i] = a[i] + b[i];
__builtin_prefetch (&a[i+j], 1, 1);
__builtin_prefetch (&b[i+j], 0, 1);
- /* ... */
+ /* @dots{} */
@}
@end smallexample
Index: tm.texi
===================================================================
RCS file: /cvsroot/gcc/gcc/gcc/doc/tm.texi,v
retrieving revision 1.102.2.4
diff -u -r1.102.2.4 tm.texi
--- tm.texi 3 May 2002 13:13:37 -0000 1.102.2.4
+++ tm.texi 22 Jun 2002 19:30:31 -0000
@@ -2564,7 +2564,7 @@
This macro defines the operation used when something is pushed
on the stack. In RTL, a push operation will be
-@code{(set (mem (STACK_PUSH_CODE (reg sp))) ...)}
+@code{(set (mem (STACK_PUSH_CODE (reg sp))) @dots{})}
The choices are @code{PRE_DEC}, @code{POST_DEC}, @code{PRE_INC},
and @code{POST_INC}. Which of these is correct depends on
--
They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety.
-- Benjamin Franklin, Historical Review of Pennsylvania, 1759