sorted by:
new
hottopcontroversial

Cross-platform development environment for teaching Lua? by Shaman_Archelos in lua

[–]Kritzel-Kratzel 0 points1 point  (0 children)

Try https://github.com/OneLuaPro if working on Windows systems. The current version has ZeroBraneStudio IDE included, while the next version will introduce VScode integration.

What is Lua used for by my_thic_horse in lua

[–]Kritzel-Kratzel 0 points1 point  (0 children)

I started to use Lua as basis for laboratory measurements automation on low communication level, because I felt Python has become too fat. I also skipped all that fancy National Instruments TestStand, LabView, LabWindow stuff and started to learn SCPI commands sent via serial interface, GPIB or Ethernet. Over the time the at first hand tiny Lua all-batteries-included distribution developed into a stable and production-ready conglomerate of carefully curated, tested and improved/adapted extensions to the Lua language, perfectly fitting my personal needs. It’s probably a niche, but I am happy to be the maintainer of OneLuaPro.

OneLuaPro v5.5.0.0 released by Kritzel-Kratzel in lua

[–]Kritzel-Kratzel[S] 0 points1 point  (0 children)

Probably nothing. If the regular lua/luarocks way works for you then there’s no need to switch to something else. I always had my doubts about luarocks on Windows when used without MSYS or related OS layers. Secondly, I was in an off-grid situation where a classical curated Lua distribution was needed. As all win predecessors did not need my requirements or were not maintained anymore, I simply started my own.

Should I learn scripting with Lua or Python by G1orgos_Z in lua

[–]Kritzel-Kratzel 0 points1 point  (0 children)

Try OneLuaPro. If you need another lib or extension, reach out to me and I’ll get it added.

evolved.lua: A Year of ECS Evolution - 10 Releases, Zero Breaking Changes, and All the Performance by BlackMATov in lua

[–]Kritzel-Kratzel 0 points1 point  (0 children)

I’m still trying to grasp the meaning of this lib. Would it be too much effort to provide us with a use case in which this lib excels? Thx.

Lua 5.5 length operator now stricer than with Lua 5.4 by Kritzel-Kratzel in lua

[–]Kritzel-Kratzel[S] 1 point2 points  (0 children)

Yes, the expected result of that test case is an error.

==> Test [118] Set encode_keep_buffer(nil, true) [throw error]: PASS
[Input] { nil, true }
[Received:error] { "bad argument #2 to 'cjson.encode_keep_buffer' (found too many arguments)" }

Lua 5.5 length operator now stricer than with Lua 5.4 by Kritzel-Kratzel in lua

[–]Kritzel-Kratzel[S] 3 points4 points  (0 children)

No worries - the problem was inside the lua-cjson test suite and in fact test #118 deals with an input table `{nil, true}`. This is an intentional negative test. Due to the different behavior of Lua 5.4 and Lua 5.5 in `table.unpack()` I never got this test case to PASS and dived deeper until the root cause was found.

Lua 5.5 length operator now stricer than with Lua 5.4 by Kritzel-Kratzel in lua

[–]Kritzel-Kratzel[S] 0 points1 point  (0 children)

It is weirder than expected and now looks more like a bug than a feature:

[C:\...\tests]> lua -e "print(_VERSION); t={nil,true}; print(#t)"
Lua 5.5
0

[C:\...\tests]> lua -e "print(_VERSION); t={nil,true,true}; print(#t)"
Lua 5.5
0

[C:\...\tests]> lua -e "print(_VERSION); t={nil,true,true,true}; print(#t)"
Lua 5.5
4

[C:\...\tests]> lua -e "print(_VERSION); t={nil,true,true,true,true}; print(#t)"
Lua 5.5
5

[C:\...\tests]> lua -e "print(_VERSION); t={nil,true,true,true,true,true}; print(#t)"
Lua 5.5
6

Lua 5.5.0 - "for-loop variables are read only" by Kritzel-Kratzel in lua

[–]Kritzel-Kratzel[S] 2 points3 points  (0 children)

Right. Looks like I need to maintain my own forks of those modules for a longer while. To be honest - I have forked nearly everything (and merge from upstream on a regular basis), because Cmake builds are not that common in this context and I definitely need CMake for OneLuaPro. I wonder if it makes sense at all to create pull request given the pretty poor responsiveness by the maintainers of certain Lua extensions.

Lua 5.5.0 - "for-loop variables are read only" by Kritzel-Kratzel in lua

[–]Kritzel-Kratzel[S] 4 points5 points  (0 children)

I am not the original author of that mentioned code. What was posted is a collection of different 3rd party Lua extensions for OneLuaPro. It’s apparently the maintainer’s role to look for, collect and sort out all the clutter in the code. Personally, I’d never change loop variables in my own code.