Re: Who is using modified Lua versions, what are they and why?

Am 27.06.2026 um 02:54 schrieb 'Sewbacca' via lua-l:
> Lua is small, readable and easily modifiable which are huge perks. 
> However they only come in handy if you are in control of the 
> application itself which is running Lua. If you rely on the default 
> distributed Lua version, you can't just change the parser. Especially 
> if you are writing modules, then you have very little control over the 
> runtime.
>
> So out of curiosity: Who is using modified Lua versions, what are the 
> modifications and why do you need them?
>
> ~ Sewbacca
> -- 
> You received this message because you are subscribed to the Google 
> Groups "lua-l" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to [email protected].
> To view this discussion visit 
> https://groups.google.com/d/msgid/lua-l/dbcab2ec-b0c0-46de-96de-68e7e7782044%40kolabnow.com 
> <https://groups.google.com/d/msgid/lua-l/dbcab2ec-b0c0-46de-96de-68e7e7782044%40kolabnow.com?utm_medium=email&utm_source=footer>.

We use a modified Lua 5.2 that supports native breakpoints. That means 
when I add a breakpoint to Lua, a breakpoint instruction is set in the 
bytecode and when the breakpoint is hit, the interpreter calls the debug 
hook. On resume or step the original instruction is executed. When I 
remove the breakpoint the original instruction is swapped back in.

The reason for this is to have a way to debug a scripts and have zero 
runtime (performance) impact until you actually hit a breakpoint.

I am still planning to do this in Lua 5.5 as a standalone patch. My 
current implementation relies on additional C++ classes.

-- 

Thomas

-- 
You received this message because you are subscribed to the Google Groups "lua-l" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion visit https://groups.google.com/d/msgid/lua-l/bf1a62fd-cebb-41c6-b3cd-00791df7e54e%40indel.ch.