require(), some parser things #13
Open
Conversation
This file contains 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
…ates booleans); functions as keys
|
hi! sounds good, i'll test this weekend, bit busy at work currently. thanks ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi.
I did some stuff to make some of my modules cooperate. In main.js, I added a packages table to get the behavior closer to stock Lua, e.g. it won't reload after re-require()'s. Not 100% accurate (other package details), but probably close enough for most uses.
I addressed a few things in the parser / library, too. tostring() returns unique keys per-function and per-table, pairs() should list booleans (a key was off), and functions should be usable as keys, now (probably wasn't necessary to hijack the bool table...). (I've sent a parallel request along to @mherkender.)