Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
patch 8.2.5003: cannot do bitwise shifts
Problem: Cannot do bitwise shifts. Solution: Add the >> and << operators. (Yegappan Lakshmanan, closes #8457)
- Loading branch information
Showing
11 changed files
with
554 additions
and
160 deletions.
There are no files selected for viewing
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
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
Oops, something went wrong.
a061f34
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So we now have two bitwise operators without corresponding functions and a set of functions with no corresponding operators. So much for consistency.
a061f34
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At least it could be made consistent, except for the OR operator. Any thoughts on that?
Any multiple character solutions don't feel right.
An out in left field thought. Have a flag that says the command separator character is
;
instead of|
. Or maybe start with:|
is deprecated now, and;
is allowed as an alternative. Or|
works inside an expression so( val1 | val2)
could work now and not need to change|
for command separator. Or combinations.I like the idea of using
;
as an alternative to|
.