Skip to content

Conversation

@sebproell
Copy link
Member

@sebproell sebproell commented May 4, 2025

This is an alternative to #733 (which is rather difficult to complete). Closes #731

@sebproell sebproell added type: bug report Issues reporting a bug in the code team: input labels May 4, 2025
@sebproell sebproell self-assigned this May 4, 2025
Copy link
Contributor

@ischeider ischeider left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You didn't change the FOUR_C_THROW calls after an if-clause into a FOUR_C_ASSERT. Is there any policy which one to use generally?

@sebproell
Copy link
Member Author

@ischeider I don't think there is a policy. Do you want to add some guidance on that? This could go into the coding guidelines. I use both styles, depending on the context. Sometimes, I want to construct a complex error message. In this case, the manual if is useful.

@sebproell sebproell merged commit 3d2d7d8 into 4C-multiphysics:main May 5, 2025
29 checks passed
@sebproell sebproell deleted the exodus-numbering-options branch May 5, 2025 07:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

team: input type: bug report Issues reporting a bug in the code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] Does the exodus read feature change the results?

3 participants