Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
From reading revision N3242 of the c++11 draft, it appears that some components of the standard library’s interfaces (notably threading and locking) depend on exception handling.
Since I do a lot of work with exceptions disabled, I am wondering which library components/features will be (practically or logically) unusable without exception handling enabled?
This question is over one month old, and unanswered.
I am providing an answer which can be considered a community wiki, add to it as needed.
std::threadSection 30.2.2. Transitive. Abstraction implemented using native implementations.std::mutex,std::recursive_mutex,std::timed_mutex,std::recursive_timed_mutex. Section 30.4.1, Intransitive if you supply your own exception free locking (viaBasicLockable,Lockable,TimedLockable). Abstraction implemented using native implementations.std::condition_variableSection 30.5. Transitive. Abstraction implemented using native implementations.note: There will be more.