Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • openfoam openfoam
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 423
    • Issues 423
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 9
    • Merge requests 9
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • openfoamopenfoam
  • Issues
  • #1780
Closed
Open
Issue created Jul 22, 2020 by Mark OLESEN@markMaintainer

FOAM_ABORT pre-empts throwing exceptions

As noted prior to release by @andy, running with FOAM_ABORT means that failed loading of function objects translates into a real failure instead of being generous and emitting a warning. With issue #1779 (closed), it looks like time to make a minor adjustment to the error class.

I think that if code has requested throwExceptions() this should be honoured by the internals of error. Ie, swap the order of if/else if in error.C around line 240.

Opinions, objections? @andy and @Mattijs

Edited Jul 22, 2020 by Mark OLESEN
Assignee
Assign to
Time tracking