Fix a preprocessor expression evaluation bug
A subexpression in parentheses lost its string/int type flag and instead used whatever type was left in the stack entry from previous use. In practice we mostly got away with this because most preprocessor expressions are integer, but it could have resulted in a preprocessor expression incorrectly evaluating as zero. If -Wextra was in use you got a warning: Warning 202: Error: 'Can't mix strings and integers in expression' Fixes #1384
This commit is contained in:
parent
471b9f734e
commit
204a5f7bf3
3 changed files with 28 additions and 0 deletions
|
|
@ -7,6 +7,17 @@ the issue number to the end of the URL: https://github.com/swig/swig/issues/
|
|||
Version 4.1.0 (in progress)
|
||||
===========================
|
||||
|
||||
2022-02-23: olly
|
||||
#1384 Fix a preprocessor expression evaluation bug. A
|
||||
subexpression in parentheses lost its string/int type flag and
|
||||
instead used whatever type was left in the stack entry from
|
||||
previous use. In practice we mostly got away with this because
|
||||
most preprocessor expressions are integer, but it could have
|
||||
resulted in a preprocessor expression incorrectly evaluating as
|
||||
zero. If -Wextra was in use you got a warning:
|
||||
|
||||
Warning 202: Error: 'Can't mix strings and integers in expression'
|
||||
|
||||
2022-02-20: wsfulton
|
||||
Fix %warnfilter warning suppress for warning 315 SWIGWARN_PARSE_USING_UNDEF.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue