Avoid the term "undefined behavior" in the manual

This commit is contained in:
Roberto Ierusalimschy 2021-06-09 13:24:49 -03:00
parent fc6c74f100
commit c0ed74c1e1

View File

@ -6365,9 +6365,8 @@ The order in which the indices are enumerated is not specified,
(To traverse a table in numerical order, (To traverse a table in numerical order,
use a numerical @Rw{for}.) use a numerical @Rw{for}.)
The behavior of @id{next} is undefined if, You should not assign any value to a non-existent field in a table
during the traversal, during its traversal.
you assign any value to a non-existent field in the table.
You may however modify existing fields. You may however modify existing fields.
In particular, you may set existing fields to nil. In particular, you may set existing fields to nil.