Repository navigation
Follow psxlua's fixed a^b and leading-zero numerals - #44
Merged
Merged
Conversation
rixnobis/psxlua#9 makes a^b a^b rather than a^(b+1), and parses 010 as 10. The host shims stop reproducing the old behaviour, and "0x" alone is now a malformed number, as in stock Lua. The three changed expected files were written by luac.ps-exe at that commit in pcsx-redux; the other fourteen come out byte-identical to the existing ones.
rixnobis
marked this pull request as ready for review
October 6, 2026 07:10
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follows rixnobis/psxlua#9:
a^bwas a^(b+1) and010failed to compile. The host shims now match the fixed code. arith_fold, operators and numbers were recompiled by luac.ps-exe in pcsx-redux; the other 14 expected files did not change.0xalone is a malformed number now, so it left numbers.lua, and the syntax-error check uses1.5.Draft until psxsplash's nugget pin has the fix. Merged before that, exported scripts using
^on constants would get different bytecode from what psxsplash compiles.