Skip to content

Bugfix/44 parsing error#46

Merged
fluidnumericsJoe merged 3 commits intomasterfrom
bugfix/44-parsing-error
Jan 26, 2026
Merged

Bugfix/44 parsing error#46
fluidnumericsJoe merged 3 commits intomasterfrom
bugfix/44-parsing-error

Conversation

@fluidnumericsJoe
Copy link
Copy Markdown
Member

Resolves #44

fluidnumericsJoe and others added 2 commits October 5, 2025 15:15
…cedence

Fix two bugs in ConvertToPostFix that caused incorrect parsing of
expressions like 'x-sqrt(x)+100':

1. Pop function token after closing parenthesis - the standard
   shunting-yard algorithm requires popping the function to output
   after the opening parenthesis is removed

2. Handle left-associative operator precedence - operators +, -, *, /
   are left-associative and should pop equal-precedence operators,
   while ^ is right-associative and should not

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@fluidnumericsJoe fluidnumericsJoe self-assigned this Jan 26, 2026
@fluidnumericsJoe fluidnumericsJoe added the bug Something isn't working label Jan 26, 2026
@codecov-commenter
Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@fluidnumericsJoe
Copy link
Copy Markdown
Member Author

Windows builds were failing previously, so this is alright. I'll open a separate issue on this to follow up on later

@fluidnumericsJoe fluidnumericsJoe merged commit 3222362 into master Jan 26, 2026
15 of 18 checks passed
@fluidnumericsJoe fluidnumericsJoe deleted the bugfix/44-parsing-error branch January 26, 2026 20:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Possible error in FEQParse

2 participants