Skip to content

Conversation

@jayrm
Copy link
Member

@jayrm jayrm commented May 21, 2018

  • boolean: don't allow NEG unary op '-' on boolean data types
  • negative booleans were allowed for compatibility with fbc test suite (prior to Jan 2018)
  • can be removed now since test-suite has been re-written
  • this change stacks on PR Fix #878: select case as const #80, only because original bug was related to boolean

jayrm added 9 commits April 28, 2018 12:06
… Case As const'

- jump tables generated by SELECT CASE AS CONST use bias/span internally, instead of minval/maxval
- SELECT CASE AS CONST respects data type used when parsing CASE range values
- CASE range values can be mix of signed & unsigned constants
- if there was some other error parsing the CASE expression, expression could be NULL
- test overflow warnings for SELECT CASE AS CONST
- test the function of parser-decl-symbtype.bas:cConstIntExprRanged()
- negative booleans were allowed for compatibility with fbc test suite (prior to Jan 2018)
- can be removed now since test-suite has been re-written
@jayrm jayrm merged commit 8a76540 into freebasic:master May 23, 2018
@jayrm jayrm deleted the boolean-no-neg branch May 23, 2018 02:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants