[Mono-devel-list] C++/CLI and .NET 2.0

[Michael Torrie]

On Thu, 2004-07-01 at 05:14, Jonathan Pryor wrote:
> <snip>
> You might want to read:
> 
> 	http://msdn.microsoft.com/msdnmag/issues/04/05/VisualC2005/default.aspx
> 
> There's the /clr:pure flag:
> 
>         The new /clr:pure compiler flag instructs the compiler to
>         generate a pure managed image with no native constructs.

If C++ programs are compiled to pure CLR apps, does that not mean that
the guaranteed destruction semantics of C++ will not apply?  If this is
the case then there are many C++ apps that would require some work if
they depend on this behavior (some of my C++ code depends on this).  I
believe this is one big reason why C++ on .NET will never be a huge
success.  Would compiling C++ via whirl allow this somewhat critical c++
feature to work on .NET?

Michael


> 
> And the /clr:safe flag:
> 
>         This is the holy grail of verifiability for C++ developers.
>         Throwing this switch causes the compiler to ensure that the
>         generated assembly is completely verifiable; any unverifiable
>         constructs will result in a compile-time error.
> 
> Both of these should permit C++/CLI code to run under Mono.  Anything
> else won't, as native code could (will?) be embedded in the assembly,
> which Mono can't handle.
> 
>  - Jon
> 
> 
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
-- 
Michael Torrie <torriem at chem.byu.edu>