* doc/as.texinfo (Statements): Remove paragraph discussing

continuing lines with a backslash.  This hasn't worked for years,
	if it ever did.
This commit is contained in:
Ian Lance Taylor 1998-07-02 20:25:45 +00:00
parent 0a3ec14442
commit 20489f152f
2 changed files with 8 additions and 11 deletions

View File

@ -1,3 +1,9 @@
Thu Jul 2 16:24:58 1998 Ian Lance Taylor <ian@cygnus.com>
* doc/as.texinfo (Statements): Remove paragraph discussing
continuing lines with a backslash. This hasn't worked for years,
if it ever did.
Thu Jul 2 14:06:22 1998 Klaus Kaempf <kkaempf@rmi.de>
* obj-vms.c: Add C++ support with ctors/dtors sections. Add weak

View File

@ -1646,16 +1646,6 @@ exception: they do not end statements.
It is an error to end any statement with end-of-file: the last
character of any input file should be a newline.@refill
@cindex continuing statements
@cindex multi-line statements
@cindex statement on multiple lines
You may write a statement on more than one line if you put a
backslash (@kbd{\}) immediately in front of any newlines within the
statement. When @code{@value{AS}} reads a backslashed newline both
characters are ignored. You can even put backslashed newlines in
the middle of symbol names without changing the meaning of your
source program.
An empty statement is allowed, and may include whitespace. It is ignored.
@cindex instructions and directives
@ -3571,7 +3561,8 @@ in @sc{ieee} format.
is ignored unless the file is assembled with debugging enabled.
Only @samp{--gstabs} is currently supported.
@var{label} is the entry point of the function and if omitted @var{name}
is used.
prepended with the @samp{leading char} is used.
@samp{leading char} is usually @code{_} or nothing, depending on the target.
All functions are currently defined to have @code{void} return type.
The function must be terminated with @code{.endfunc}.