Comments on: Bjarne Stroustrup on C++/CLI http://blog.stevex.net/2006/08/bjarne-stroustrup-on-ccli/ Software development and other notes. Tue, 15 Jun 2010 13:44:34 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Peter Ritchie http://blog.stevex.net/2006/08/bjarne-stroustrup-on-ccli/comment-page-1/#comment-14280 Peter Ritchie Sat, 09 Sep 2006 16:13:19 +0000 http://blog.stevex.net/index.php/2006/08/22/bjarne-stroustrup-on-ccli/#comment-14280 I think what Bjarne is trying to say is to have an abstraction layer of C++/CLI code that provides access to ISO C++ code (i.e. code that is not publicly available at the assembly level or uses .NET classes). C++/CLI will perform all the PInvoke between the CLI class and the ISO C++ classes automatically with C++ interop. This, of course, depends on your goals. If you *never* plan on using the ISO C++ code in anything other than managed application, forcing it the be PInvoked adds a slight performance hit for no reason. Arguably a premature optimization to push C++ code that does not access .NET classes or CLI features into C++/CLI... Although Bjarne puts a heavy preference to writing "portable" code, using ISO C++ over C++/CLI forces the code to be compiled for a specific processor, making the assembly essentially not portable, depending on the platform to which it is deployed. I think what Bjarne is trying to say is to have an abstraction layer of C++/CLI code that provides access to ISO C++ code (i.e. code that is not publicly available at the assembly level or uses .NET classes). C++/CLI will perform all the PInvoke between the CLI class and the ISO C++ classes automatically with C++ interop.

This, of course, depends on your goals. If you *never* plan on using the ISO C++ code in anything other than managed application, forcing it the be PInvoked adds a slight performance hit for no reason. Arguably a premature optimization to push C++ code that does not access .NET classes or CLI features into C++/CLI…

Although Bjarne puts a heavy preference to writing “portable” code, using ISO C++ over C++/CLI forces the code to be compiled for a specific processor, making the assembly essentially not portable, depending on the platform to which it is deployed.

]]>