RC for next version #34
Merged
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
…ll the wrapper code is anywya. 2. Moved the new hash table here. 3. Did a lot of polish, partially around ropes / tables. 4. Finally integrated the mac process info stuff. 5. Moved around a bunch of the C code to be better organized. 6. Moved all the one-off test cases to nimutils.nim, and now have it produce an exe There are some minor breaking changes in here.
…orted function seems to clober local variables in templates? Conform tok() function was picking up the s() from here where it needs the 's' object in lex()
…e modules to get through, but am nearly done.
… debugging tools, and so on. Needs a bit more documentation for the new stuff. Also, I found a new bug while adding this stuff... in some cases margins get eaten when a real container is inside a formatting box. Will fix soon.
… any kind! Now I just have to update everything else :(
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.
Lots of polish work:
#3 was the hardest... basically I kept trying to figure out what was happening, so kept rewriting bits more cleanly, and eventually seemed like it was worth finishing #4.
And now, for at least 5 minutes, I don't know of any rendering issues (even in the release I knew of a couple but there were workarounds for anything that would show).