I've actually taken the throw clauses out of the .NET library in source
control. It rather makes sense since the other .NET languages do not
support throw clauses, so there really isn't any reason for Managed C++
to support them. The unmanaged throw clauses are still supported.
--oren
Caleb Epstein wrote:
> On 1/5/06, *Andrei Goldchleger* <an...@gm...
> <mailto:an...@gm...>> wrote:
>
> I am running into problems when compiling QF (1.10.2) solution in the
> new VS 2005. The C++ compiler seem to dislike throw clauses at method
> declarations on managed C++, or something like that.
>
> http://msdn2.microsoft.com/library/7tfey5a9.aspx
>
> Does anyone know if this can be overridden in any way?
>
>
> I ran into this myself, and I don't think there's any way to disable
> it. I think all the throw decls will need to be conditionally
> compiled-out when building for .NET.
>
> --
> Caleb Epstein
> caleb dot epstein at gmail dot com
|