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

Why do we name fail in [iostate.flags]? #674

Closed
jwakely opened this issue Apr 5, 2016 · 2 comments
Closed

Why do we name fail in [iostate.flags]? #674

jwakely opened this issue Apr 5, 2016 · 2 comments

Comments

@jwakely
Copy link
Member

jwakely commented Apr 5, 2016

Otherwise, the function throws an object fail of class basic_ios::failure (27.5.3.1.1), constructed with implementation-defined argument values.

Why do we name it at all, and why do we give it the same name as a member function of the current class?
@AlisdairM
Copy link
Contributor

It looks suspect to me too.

@jwakely
Copy link
Member Author

jwakely commented Jun 22, 2016

Fixed by 24ad083

@jwakely jwakely closed this as completed Jun 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@AlisdairM @jwakely