This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libstdc++/66145] [5/6/7 Regression] std::ios_base::failure objects thrown from libstdc++.so use old ABI


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66145

--- Comment #15 from Boris Kolpackov <boris at kolpackov dot net> ---
> And I still think using exceptions in iostreams is dumb in the first place.

I am interested to hear what is your recommendation to do instead, call good()
after every IO operation?

In fact, I think that with inheritance from system_error iostream exceptions
finally got (barely) usable. But because of this bug (which is now pervasive)
we will probably have to scrap the use of exceptions. So I am genuinely
interested to hear about the alternatives/recommendations.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]