Re: [Mingw-w64-public] throw(...) in MinGW

question can throw an exception. That sounds quite useless to me IMHO. Just remove it, or ifdef a THROWS macro or some such. Cheers, Ruben > *From:* Ruben Van Boxem > *Sent:* Monday, June 29, 2015 2:27 AM > *To:* mingw-w64-public@lists.sourceforge.net > *Subject:* Re: [Mingw-w64-pub

Re: [Mingw-w64-public] throw(...) in MinGW

Thanks Ruben for the help. To answer your question, yes, I am. I was also using -std=gnu++14. However, I am now compiling only with –std::c++11, but to no avail. From: Ruben Van Boxem Sent: Monday, June 29, 2015 2:27 AM To: mingw-w64-public@lists.sourceforge.net Subject: Re: [Mingw-w64-public

Re: [Mingw-w64-public] throw(...) in MinGW

Op 29-jun.-2015 07:32 schreef : > > In VS2013, I declare the member functions like this: > void setString(const std::wstring& _str) throw(...); > > But now that I am switching to MinGW, I get a complain from the compiler saying: > error: expected type-specifier before '...' token > throw(...) { > >

[Mingw-w64-public] throw(...) in MinGW

In VS2013, I declare the member functions like this: void setString(const std::wstring& _str) throw(...); But now that I am switching to MinGW, I get a complain from the compiler saying: error: expected type-specifier before '...' token throw(...) { How can I fix this problem? Thanks --- This e