| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
uint16; fixes #7654
|
| |
|
| |
|
|
|
|
| |
combination with the ddot calling syntax
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
|
|
|
| |
literals or comments
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
if it wasn't for bug #3978, assignment from getNumber would overwrite
tok.indent (which is set at top of rawGetTok, but not in getNumber)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
- The char(-1) < char(0) is not covered in this PR - different beast.
- Additionally to #1179, I found that non base-10 literals wheren't bounds checked at all.
|
| |
|
|\
| |
| | |
Bugfix #2523 number literal lexing
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|