[Mono-devel-list] C++/CLI and .NET 2.0
torriem at chem.byu.edu
Thu Jul 1 21:21:48 EDT 2004
On Thu, 2004-07-01 at 05:14, Jonathan Pryor wrote:
> You might want to read:
> 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?
> 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
Michael Torrie <torriem at chem.byu.edu>
More information about the Mono-devel-list