This is the mail archive of the gcc-patches@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]

Re: [3.3] Followup to C++ forced unwinding


Zack Weinberg <zack@codesourcery.com> writes:

| Mark Mitchell <mark@codesourcery.com> writes:
| 
| > (1) The libsupc++ bits make:
| >
| >       void f() throw () { read (...); }
| >   
| >     be handled just like:
| >
| >       void f() throw () { throw 3; }
| >  
| >     would.
| 
| Query, is there a way to write "this function may be cancelled but
| otherwise will not throw an exception"?  Notation like
| 
| void f() throw (cxxabi::thread_cancellation) { ... }

hmm, assuming current C++ semantics with repesct to ES, I don't think
that helps much.  Or do you have any specific extension in mind?

-- Gaby


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