Manual corrected with the new syntax for attributes

Commit 0d52913804, with the change in the syntax of attributes,
did not update the manual accordingly.
This commit is contained in:
Roberto Ierusalimschy
2019-08-16 16:11:21 -03:00
parent b96b0b5abb
commit 45948e7e55

View File

@@ -1499,13 +1499,13 @@ The declaration can include an initialization:
@Produc{ @Produc{
@producname{stat}@producbody{@Rw{local} attnamelist @bnfopt{@bnfter{=} explist}} @producname{stat}@producbody{@Rw{local} attnamelist @bnfopt{@bnfter{=} explist}}
@producname{attnamelist}@producbody{ @producname{attnamelist}@producbody{
attrib @bnfNter{Name} @bnfrep{@bnfter{,} attrib @bnfNter{Name}}} @bnfNter{Name} attrib @bnfrep{@bnfter{,} @bnfNter{Name} attrib}}
} }
If present, an initial assignment has the same semantics If present, an initial assignment has the same semantics
of a multiple assignment @see{assignment}. of a multiple assignment @see{assignment}.
Otherwise, all variables are initialized with @nil. Otherwise, all variables are initialized with @nil.
Each variable name may be preceded by an attribute Each variable name may be postfixed by an attribute
(a name between angle brackets): (a name between angle brackets):
@Produc{ @Produc{
@producname{attrib}@producbody{@bnfopt{@bnfter{<} @bnfNter{Name} @bnfter{>}}} @producname{attrib}@producbody{@bnfopt{@bnfter{<} @bnfNter{Name} @bnfter{>}}}
@@ -1514,7 +1514,7 @@ There are two possible attributes:
@id{const}, which declares a @x{constant variable}, @id{const}, which declares a @x{constant variable},
that is, a variable that cannot be assigned to that is, a variable that cannot be assigned to
after its initialization; after its initialization;
and @id{toclose}, which declares a to-be-closed variable @see{to-be-closed}. and @id{close}, which declares a to-be-closed variable @see{to-be-closed}.
A list of variables can contain at most one to-be-closed variable. A list of variables can contain at most one to-be-closed variable.
A chunk is also a block @see{chunks}, A chunk is also a block @see{chunks},
@@ -1569,7 +1569,7 @@ Similarly, if a coroutine ends with an error,
it does not unwind its stack, it does not unwind its stack,
so it does not close any variable. so it does not close any variable.
In both cases, In both cases,
you should either use finalizers you can either use finalizers
or call @Lid{coroutine.close} to close the variables. or call @Lid{coroutine.close} to close the variables.
However, if the coroutine was created However, if the coroutine was created
through @Lid{coroutine.wrap}, through @Lid{coroutine.wrap},
@@ -9066,7 +9066,7 @@ and @bnfNter{LiteralString}, see @See{lexical}.)
} }
@producname{attnamelist}@producbody{ @producname{attnamelist}@producbody{
attrib @bnfNter{Name} @bnfrep{@bnfter{,} attrib @bnfNter{Name}}} @bnfNter{Name} attrib @bnfrep{@bnfter{,} @bnfNter{Name} attrib}}
@producname{attrib}@producbody{@bnfopt{@bnfter{<} @bnfNter{Name} @bnfter{>}}} @producname{attrib}@producbody{@bnfopt{@bnfter{<} @bnfNter{Name} @bnfter{>}}}