lua-l archive
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
] [
Date Index
] [
Thread Index
]
Subject
:
Re: string.dump(f, true) does not work as expected
From
: Brigham Toskin <brighamtoskin@
...
>
Date
: Wed, 10 Jun 2015 10:05:24 -0700
OS X 10.8.5, lua command line REPL...
Lua 5.1.5 --> false
Lua 5.2.3 --> false
Lua 5.3.0 --> true
LuaJIT 2.0.2 --> true
On Wed, Jun 10, 2015 at 5:17 AM, Egor Skriptunoff
<
egor.skriptunoff@gmail.com
>
wrote:
IMO, line# where function has been defined is a part of debug info and should be stripped out.
I'd agree with this, unless the bytecode loader absolutely depends on it for some reason. But I'd probably call that a design bug, anyway.
--
Brigham Toskin
Follow-Ups
:
Re: string.dump(f, true) does not work as expected
,
Roberto Ierusalimschy
References
:
string.dump(f, true) does not work as expected
,
Egor Skriptunoff
Re: string.dump(f, true) does not work as expected
,
Luiz Henrique de Figueiredo
Re: string.dump(f, true) does not work as expected
,
Egor Skriptunoff
Prev by Date:
Re: How to disable hooks?
Next by Date:
Re: Definition of a sequence
Previous by thread:
Re: string.dump(f, true) does not work as expected
Next by thread:
Re: string.dump(f, true) does not work as expected
Index(es):
Date
Thread