/clr vs /clr pure

  • Thread starter Thread starter Peter Oliphant
  • Start date Start date
P

Peter Oliphant

I've gotten my application to compile under '/clr'. I then tried '/clr pure'
and it compiled immedately with no changes. What should I consider when
deciding which of these two option to compile under? Are there advantages
and disadvantages to one over the other?

I also tried compiling it using the '/clr safe' option and got 6420 errors
(no, that's not the error number, that's the number of errors). So don't
think I'll go that route just yet...lol

[==P==]
 
If you don't need to have MFC or ATL support, it might be a good idea to use
/clr:pure, since the lack of managed/unmanaged transitions might actually
give you better performance.
 
clr/pure is a great way to make sure that your app/dll provides a completely
managed interface to other exes/dlls. At the same time, clr/pure allows the
exe/dll to call unmanaged functions. It's great for wrappers.
 
Back
Top