update to 5.3.5 rc2

README

@@ -1,5 +1,5 @@
 
-This is Lua 5.3.5, released on 25 Jun 2018.
+This is Lua 5.3.5, released on 26 Jun 2018.
 
 For installation instructions, license details, and
 further information about Lua, see doc/readme.html.

doc/manual.html

@@ -35,7 +35,7 @@ <H1>
 <!-- ====================================================================== -->
 <p>
 
-<!-- $Id: manual.of,v 1.167.1.1 2017/05/08 18:18:34 roberto Exp $ -->
+<!-- $Id: manual.of,v 1.167.1.2 2018/06/26 15:49:07 roberto Exp $ -->
 
 
 
@@ -1823,17 +1823,17 @@ <h2>3.4 &ndash; <a name="3.4">Expressions</a></h2>
      g(f(), x)          -- f() is adjusted to 1 result
      g(x, f())          -- g gets x plus all results from f()
      a,b,c = f(), x     -- f() is adjusted to 1 result (c gets nil)
-     a,b = ...          -- a gets the first vararg parameter, b gets
+     a,b = ...          -- a gets the first vararg argument, b gets
                         -- the second (both a and b can get nil if there
-                        -- is no corresponding vararg parameter)
+                        -- is no corresponding vararg argument)
 
      a,b,c = x, f()     -- f() is adjusted to 2 results
      a,b,c = f()        -- f() is adjusted to 3 results
      return f()         -- returns all results from f()
-     return ...         -- returns all received vararg parameters
+     return ...         -- returns all received vararg arguments
      return x,y,f()     -- returns x, y, and all results from f()
      {f()}              -- creates a list with all results from f()
-     {...}              -- creates a list with all vararg parameters
+     {...}              -- creates a list with all vararg arguments
      {f(), nil}         -- f() is adjusted to 1 result
 </pre>
 
@@ -2034,9 +2034,9 @@ <h3>3.4.4 &ndash; <a name="3.4.4">Relational Operators</a></h3><p>
 A closure is always equal to itself.
 Closures with any detectable difference
 (different behavior, different definition) are always different.
-Closures created at different times but no detectable differences
+Closures created at different times but with no detectable differences
 may be classified as equal or not
-(depending on internal cashing details).
+(depending on internal caching details).
 
 
 <p>
@@ -2298,7 +2298,7 @@ <h3>3.4.10 &ndash; <a name="3.4.10">Function Calls</a></h3><p>
 then this function is called
 with the given arguments.
 Otherwise, the prefixexp "call" metamethod is called,
-having as first parameter the value of prefixexp,
+having as first argument the value of prefixexp,
 followed by the original call arguments
 (see <a href="#2.4">&sect;2.4</a>).
 
@@ -2876,7 +2876,7 @@ <h2>4.6 &ndash; <a name="4.6">Error Handling in C</a></h2>
 as it should be already protected.
 However,
 when C code operates on other Lua states
-(e.g., a Lua parameter to the function,
+(e.g., a Lua argument to the function,
 a Lua state stored in the registry, or
 the result of <a href="#lua_newthread"><code>lua_newthread</code></a>),
 it should use them only in API calls that cannot raise errors.
@@ -3365,7 +3365,7 @@ <h2>4.8 &ndash; <a name="4.8">Functions and Types</a></h2>
 Destroys all objects in the given Lua state
 (calling the corresponding garbage-collection metamethods, if any)
 and frees all dynamic memory used by this state.
-On several platforms, you may not need to call this function,
+In several platforms, you may not need to call this function,
 because all resources are naturally released when the host program ends.
 On the other hand, long-running programs that create multiple states,
 such as daemons or web servers,
@@ -5579,7 +5579,7 @@ <h2>4.9 &ndash; <a name="4.9">The Debug Interface</a></h2>
 
 
 <p>
-To get information about a function you push it onto the stack
+To get information about a function, you push it onto the stack
 and start the <code>what</code> string with the character '<code>&gt;</code>'.
 (In that case,
 <code>lua_getinfo</code> pops the function from the top of the stack.)
@@ -6457,7 +6457,7 @@ <h2>5.1 &ndash; <a name="5.1">Functions and Types</a></h2>
 
 <p>
 Pushes onto the stack the field <code>e</code> from the metatable
-of the object at index <code>obj</code> and returns the type of pushed value.
+of the object at index <code>obj</code> and returns the type of the pushed value.
 If the object does not have a metatable,
 or if the metatable does not have this field,
 pushes nothing and returns <code>LUA_TNIL</code>.
@@ -6744,7 +6744,7 @@ <h2>5.1 &ndash; <a name="5.1">Functions and Types</a></h2>
 the macro results in the default <code>dflt</code>.
 Otherwise, it results in the result of calling <code>func</code>
 with the state <code>L</code> and the argument index <code>arg</code> as
-parameters.
+arguments.
 Note that it evaluates the expression <code>dflt</code> only if needed.
 
 
@@ -8675,7 +8675,7 @@ <h4>Character Class:</h4><p>
 <p>
 You can put a closing square bracket in a set
 by positioning it as the first character in the set.
-You can put an hyphen in a set
+You can put a hyphen in a set
 by positioning it as the first or the last character in the set.
 (You can also use an escape for both cases.)
 
@@ -9077,8 +9077,8 @@ <h2>6.6 &ndash; <a name="6.6">Table Manipulation</a></h2>
 
 
 <p>
-Returns a new table with all parameters stored into keys 1, 2, etc.
-and with a field "<code>n</code>" with the total number of parameters.
+Returns a new table with all arguments stored into keys 1, 2, etc.
+and with a field "<code>n</code>" with the total number of arguments.
 Note that the resulting table may not be a sequence.
 
 
@@ -9210,7 +9210,7 @@ <h2>6.7 &ndash; <a name="6.7">Mathematical Functions</a></h2>
 <p>
 
 Returns the arc tangent of <code>y/x</code> (in radians),
-but uses the signs of both parameters to find the
+but uses the signs of both arguments to find the
 quadrant of the result.
 (It also handles correctly the case of <code>x</code> being zero.)
 
@@ -9511,7 +9511,7 @@ <h2>6.8 &ndash; <a name="6.8">Input and Output Facilities</a></h2>
 (plus an error message as a second result and
 a system-dependent error code as a third result)
 and some value different from <b>nil</b> on success.
-On non-POSIX systems,
+In non-POSIX systems,
 the computation of the error message and error code
 in case of errors
 may be not thread safe,
@@ -9548,7 +9548,7 @@ <h2>6.8 &ndash; <a name="6.8">Input and Output Facilities</a></h2>
 and sets its handle as the default input file.
 When called with a file handle,
 it simply sets this file handle as the default input file.
-When called without parameters,
+When called without arguments,
 it returns the current default input file.
 
 
@@ -9575,7 +9575,7 @@ <h2>6.8 &ndash; <a name="6.8">Input and Output Facilities</a></h2>
 The call <code>io.lines()</code> (with no file name) is equivalent
 to <code>io.input():lines("*l")</code>;
 that is, it iterates over the lines of the default input file.
-In this case it does not close the file when the loop ends.
+In this case, the iterator does not close the file when the loop ends.
 
 
 <p>
@@ -9958,7 +9958,7 @@ <h2>6.9 &ndash; <a name="6.9">Operating System Facilities</a></h2>
 
 
 <p>
-On non-POSIX systems,
+In non-POSIX systems,
 this function may be not thread safe
 because of its reliance on C&nbsp;function <code>gmtime</code> and C&nbsp;function <code>localtime</code>.
 
@@ -10158,7 +10158,7 @@ <h2>6.9 &ndash; <a name="6.9">Operating System Facilities</a></h2>
 
 
 <p>
-On POSIX systems,
+In POSIX systems,
 this function also creates a file with that name,
 to avoid security risks.
 (Someone else might create the file with wrong permissions
@@ -10296,8 +10296,8 @@ <h2>6.10 &ndash; <a name="6.10">The Debug Library</a></h2>
 following the order that they are declared in the code,
 counting only the variables that are active
 in the current scope of the function.
-Negative indices refer to vararg parameters;
--1 is the first vararg parameter.
+Negative indices refer to vararg arguments;
+-1 is the first vararg argument.
 The function returns <b>nil</b> if there is no variable with the given index,
 and raises an error when called with a level out of range.
 (You can call <a href="#pdf-debug.getinfo"><code>debug.getinfo</code></a> to check whether the level is valid.)
@@ -10395,7 +10395,7 @@ <h2>6.10 &ndash; <a name="6.10">The Debug Library</a></h2>
 
 
 <p>
-When the hook is called, its first parameter is a string
+When the hook is called, its first argument is a string
 describing the event that has triggered its call:
 <code>"call"</code> (or <code>"tail call"</code>),
 <code>"return"</code>,
@@ -10625,7 +10625,7 @@ <h1>7 &ndash; <a name="7">Lua Standalone</a></h1>
 </pre><p>
 will print "<code>-e</code>".
 If there is a script,
-the script is called with parameters
+the script is called with arguments
 <code>arg[1]</code>, &middot;&middot;&middot;, <code>arg[#arg]</code>.
 (Like all chunks in Lua,
 the script is compiled as a vararg function.)
@@ -10811,7 +10811,7 @@ <h2>8.2 &ndash; <a name="8.2">Changes in the Libraries</a></h2>
 <code>frexp</code>, and <code>ldexp</code>.
 You can replace <code>math.pow(x,y)</code> with <code>x^y</code>;
 you can replace <code>math.atan2</code> with <code>math.atan</code>,
-which now accepts one or two parameters;
+which now accepts one or two arguments;
 you can replace <code>math.ldexp(x,exp)</code> with <code>x * 2.0^exp</code>.
 For the other operations,
 you can either use an external library or
@@ -10846,7 +10846,7 @@ <h2>8.3 &ndash; <a name="8.3">Changes in the API</a></h2>
 <ul>
 
 <li>
-Continuation functions now receive as parameters what they needed
+Continuation functions now receive as arguments what they needed
 to get through <code>lua_getctx</code>,
 so <code>lua_getctx</code> has been removed.
 Adapt your code accordingly.
@@ -10972,7 +10972,7 @@ <h1>9 &ndash; <a name="9">The Complete Syntax of Lua</a></h1>
 
 <P CLASS="footer">
 Last update:
-Mon Jun 18 22:58:52 -03 2018
+Tue Jun 26 13:16:37 -03 2018
 </P>
 <!--
 Last change: revised for Lua 5.3.5