Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

"ios_base::failure" vs. "ios::failure" vs. "basic_ios::failure" #3306

Closed
gennaroprota opened this issue Oct 19, 2019 · 0 comments · Fixed by #3308
Closed

"ios_base::failure" vs. "ios::failure" vs. "basic_ios::failure" #3306

gennaroprota opened this issue Oct 19, 2019 · 0 comments · Fixed by #3308
Assignees
@jensmaurer

Comments

@gennaroprota
Copy link

When mentioning stream exceptions, the standard "oscillates" between "ios_base::failure", "ios::failure" and "basic_ios::failure".

In fact, these all refer to ios_base::failure, which is inherited by basic_ios (ios, of course, is
just an alias for basic_ios< char >).

For clarity and consistency, I'd recommend using "ios_base::failure" everywhere.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jensmaurer jensmaurer

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[numerics,input.output] Consistently use ios_base::failure. jensmaurer/draft
2 participants
@gennaroprota @jensmaurer