LÖVE

yetneverdone wrote: ↑Sun Nov 21, 2021 3:19 am I forgot that youre developing Gloa. Im really excited for that language. It might be my defacto language for love.
Is there anything you need help with that? perhaps with testing?

I missed this part of the reply. I'm glad you're excited about Gloa.

The development on it is really slow since I'm working on a bunch of other projects at the same time, and I don't need help with anything in particular that can involve other people. It would be nice if people played around with the language a bit and came back with some general thoughts about it, but since there's not really any documentation for anything yet it's probably too much to ask for at this point, not to mention many things may still change before I'd consider it ready to be used by people other than myself. But, thanks for offering help.

Update 1.18

Changes since 1.17:

Library:

• Added functions: loadResource(), evaluate(), pairsSorted(), sortNatural() and compareNatural().
• $symbol now accepts callable tables in addition to functions.
• Argument expressions for macros are no longer validated. This was inconsistent before as they were only validated when not containing preprocessor code, like @@foo(!!(bar)).

Awesome! Now i need to think if there are parts in my code where i can utilize that `loadResource`

Update 1.19

Changes since 1.18:

Library:

• All uses of `!` now work in macros.
• Added functions: getIndentation(), getCurrentIndentationInOutput(), getOutputSoFarOnLine(), writeFile().
• Added function readFile() as alias for getFileContents(). (The latter is now deprecated.)
• Added environment argument to evaluate().
• `pp.metaEnvironment` is now only a shallow copy of _G (i.e. `pp.metaEnvironment.io == _G.io` etc.).
• LuaJIT: Added support for binary numerals (i.e. 0b110010).

Update 1.20

Changes since 1.19:

Library:

• getOutputSoFar() can now take an output buffer argument.
• Detecting duplicate names in dual code: !!x, x = ...
• Fixed evaluate() sometimes raising an error instead of returning it.
• Fixed issue with files not ending with a newline.
• Fixed silly internal error when Lua 5.2+ was used.

Command line program:

• Added options: --version, --help.
• Added "alldone" message.
• --meta can now take a file path.
• Fixed silly internal error when Lua 5.2+ was used.

Update 1.21

Changes since 1.20:

Library:

• Added params.strictMacroArguments (which is enabled by default). Macro arguments are validated to be Lua expressions once again, unless strictMacroArguments is disabled.
• Added the metaprogram code as an argument to params.onBeforeMeta().
• Added functions: callMacro(), isProcessing().
• params.onBeforeMeta() is now only called, and *.meta.lua files are only written, if processing is necessary (i.e. not for plain Lua files in most cases).
• Plain Lua files should process a bit faster.
• Checking that params.pathMeta isn't the same as the input or output path.
• Error messages showing lots of code are now shortened.
• Fixed evaluate() treating empty code as a valid expression.

Command line program:

• Added option: --nostrictmacroarguments.
• Added the metaprogram code as an argument to the "beforemeta" message handler.
• The "beforemeta" message is now only sent, and *.meta.lua files are only written, if processing is necessary (i.e. not for plain Lua files in most cases).

Hi, just gonna share here the now public repo of my project which uses luapreprocess a lot for other devs. https://github.com/flamendless/GoingHomeRevisited

I will be moving to a new repo to rework from the ground up the game.

Im still not sure whether to use luapreprocess again or go back to plain lua. One thing that makes me not use lpp anymore is the lack of proper syntax highlighting (using treesitter) for my neovim setup (i know it's not a good reason, but my OCD just hits :/ ).

I wish i have the time to extend the lua treesitter for this one :/