Some changes and additions for numbers #358
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
rename mod on rem see PR#353
Changed binary-op string from "<<" on ">>" for correct ash right compilation
restricted implementation - only binary-op
|
Looks great as always 👍 |
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.
Fixed
integer-to-stringfor corrected parsebignumber. Current function withmod, parsed(expt 10 65)as:Path fixed it. Now
(expt 10 65)parsed ascodegenerator.lisp
Fixed incorrect binary-op string for compilation ASH function (shift right)
compiler.lisp
Added implementation of the next standard functions: ASH, LOGAND, LOGXOR, LOGNOT.
Function LOGIOR not released. The reason for this, is the birth trauma of the
reader; it incorrectly reads the symbol|at compilation. There are no ideas how to fix it, and whether it is necessary to fix it. Maybe later, somehow...Test cases added.