Updated moonsharp-luaparse, which now supports additional MoonSharp specific syntax:
!= as an alternative to ~=
Comma separated index list i.e. some_userdata[1, 2, 3]
The latter of which is a MoonSharp extension that only works for userdata so is only useful if at some point Berserk want to take advantage of the syntax.
Additionally, luabundle has been updated and now includes custom errors (rather than just textual errors). Thus if something goes wrong during bundling/unbundling we can tell which module had the problem and the underlying cause. As a result, we now have special case handling for Lua syntax errors that are encountered during bundling. In which case we bring up a notification explaining that there's a syntax error and have a "Jump to Error" button e.g.
Updated
moonsharp-luaparse, which now supports additional MoonSharp specific syntax:!=as an alternative to~=some_userdata[1, 2, 3]The latter of which is a MoonSharp extension that only works for
userdataso is only useful if at some point Berserk want to take advantage of the syntax.Additionally,
luabundlehas been updated and now includes custom errors (rather than just textual errors). Thus if something goes wrong during bundling/unbundling we can tell which module had the problem and the underlying cause. As a result, we now have special case handling for Lua syntax errors that are encountered during bundling. In which case we bring up a notification explaining that there's a syntax error and have a "Jump to Error" button e.g.