+2001-11-03 Joseph S. Myers <jsm28@cam.ac.uk>
+
+ * doc/extend.texi, doc/gcc.texi, doc/install.texi, doc/tm.texi:
+ Use "invalid" instead of "illegal". Use @r in comments in
+ examples.
+
2001-11-02 Neil Booth <neil@daikokuya.demon.co.uk>
* c-decl.c (pushdecl): Move block inside if conditional to remove
struct foo @{ int x; int y[]; @};
struct bar @{ struct foo z; @};
-struct foo a = @{ 1, @{ 2, 3, 4 @} @}; // Legal.
-struct bar b = @{ @{ 1, @{ 2, 3, 4 @} @} @}; // Illegal.
-struct bar c = @{ @{ 1, @{ @} @} @}; // Legal.
-struct foo d[1] = @{ @{ 1 @{ 2, 3, 4 @} @} @}; // Illegal.
+struct foo a = @{ 1, @{ 2, 3, 4 @} @}; // @r{Valid.}
+struct bar b = @{ @{ 1, @{ 2, 3, 4 @} @} @}; // @r{Invalid.}
+struct bar c = @{ @{ 1, @{ @} @} @}; // @r{Valid.}
+struct foo d[1] = @{ @{ 1 @{ 2, 3, 4 @} @} @}; // @r{Invalid.}
@end example
@node Variable Length
a ``bit bucket''. If you do not define this macro, GCC will use
@samp{/dev/null} as the bit bucket. If the target does not support a
bit bucket, this should be defined to the null string, or some other
-illegal filename. If the bit bucket is not writable, GCC will use a
+invalid filename. If the bit bucket is not writable, GCC will use a
temporary file instead.
@findex COLLECT_EXPORT_LIST
that omitting the type means @code{int}; this assumption worked for C89 but
is wrong for C++, and is now wrong for C99 also.
-@command{g++} accepts such (illegal) constructs with the option
+@command{g++} accepts such (invalid) constructs with the option
@option{-fpermissive}; it
will assume that any missing type is @code{int} (as defined by C89).
@item CLASS_CANNOT_CHANGE_MODE_P(@var{from}, @var{to})
A C expression that is true if, for a register in
-@code{CLASS_CANNOT_CHANGE_MODE}, the requested mode punning is illegal.
+@code{CLASS_CANNOT_CHANGE_MODE}, the requested mode punning is invalid.
For the example, loading 32-bit integer or floating-point objects into
floating-point registers on the Alpha extends them to 64-bits.