Re: string.dump(f, true) does not work as expected

[Ignacio Burgueño <iburgueno@...>]

On Wed, Jun 10, 2015 at 2:51 PM, Roberto Ierusalimschy <roberto@inf.puc-rio.br> wrote:

...

Even if the functions were equal according to the language, string.dump
still could give different results. For instance, it saves constants
by dumping their memory contents. Sometimes a constant type need
padding (e.g., long double on many Intel CPUs). Instructions themselves
sometimes do not use all fields; like padding, unused fields are free
to have any random garbage. That random content can make the result of
string.dump non deterministic. Why would that be a bug?

Not commenting on string.dump giving different results but on retaining some debug info.

Is this (not stripping all info) a bug indeed or should the wording in the manual be changed?

Currently, it says [1] that "... the binary representation is created without debug information about the function (local variable names, lines, etc.)." 

[1]: http://www.lua.org/manual/5.3/manual.html#pdf-string.dump