Looks cool. It reminds me a lot of teleko (for Löve 0.9).

groverburger wrote: ↑

Thu Jan 21, 2021 12:12 am

grump, there does appear to be some default depth buffer.

Only in some graphics drivers, I believe.

It's a pretty minimal example, but yeah, the attitude... Looking into the code, it looks to me that the main problem is the overcomplicating of formulas, resulting in incorrect output (like, pi squared??), and the improper use of origin x and y (confusion of variables, it uses the one for v instead ...

It's basic table indexing. The select() is there just for accessing the third element directly. This works too:

By save directory, you mean what would normally be ~/.love/game_id/ ? I mean whatever love.filesystem.getSaveDirectory () returns, or any subdirectory inside that. I think it defaults to ~/.local/share/love/game_id/ on Linux. Note I haven't tried this, I've just seen it mentioned in this forum at s...

Technically, the POSIX requirement is only for one platform, so I'd only need to build one binary library. For which platform? Linux? Android? MacOS? iOS? All four can handle POSIX signals. Basically, all the platforms Löve supports except Windows. How does one include and distribute those compiled...

You can install and require luaposix, then just call its functions. Distribution is going to be a problem, though, as binary libraries need to be included for all POSIX platforms you intend to support. But if it's for your own use, no problem.

not can be stacked more than twice, just saying that more than two should parse fine as well. :3 Indeed, that's pretty common with e.g. flux, see https://gist.github.com/rxi/11265117#file-tinysquares-lua-L19 This sounds like it's going to be an endless whack-a-bug. Luacheck's parser already covers ...

I've written sort of a tutorial on metatables: https://codeberg.org/pgimeno/Gists/src/ ... e-tutorial

It covers most of the fine details of how metatables work, including some advanced aspects.

MrFariator wrote: ↑

Wed Jan 13, 2021 5:22 pm

Code: Select all

  __call = function(master, child) end

Are you sure that's correct? You're defining __call as a global. I haven't seen the OP's code though, so maybe it makes more sense in the context of the program.