Talk About Network

Google


Register and Login
Nick
Password
Register create new account Sign up is FREE and you can post replies, new topics, bookmark posts and more!
Recover lost password


Programming > C++ Moderated > Re: A Design Ra...
Latest [ Topics | Posts ] Archive Post A New Topic Post a Reply
<< Topic < Post Post 4 of 4 Topic 6659 of 9909
Post > Topic >>

Re: A Design Rationale for C++/CLI

by "Andrew Browne" <clcppm-poster@[EMAIL PROTECTED] > Feb 22, 2006 at 04:21 PM

Dilip wrote:
>
> This post was around 10/2004 -- I have no idea if C++/CLI that was
> released along with .NET 2.0 around 11/2005 allows you to  
> instantiate a
> native C++ type with gcnew.

As the rationale says, this is not currently implemented in C++/CLI,
but may be in the future. The same thing applies to allocating a CLI
object on the native heap with new.

It has been suggested that the latter facility would allow a C++
program to use CLI types without even requiring the "sprinkling of
gcnew and ^" that is the minimum extended syntax currently required.
I'm not sure, however, whether this suggestion takes account of the
fact that the member functions of a CLI type typically have handle
arguments and handle return types.

Andrew


      [ See http://www.gotw.ca/resources/clcm.htm
for info about ]
      [ comp.lang.c++.moderated.    First time posters: Do this! ]
 




 4 Posts in Topic:
A Design Rationale for C++/CLI
Herb Sutter <hsutter@[  2006-02-19 06:35:56 
Re: A Design Rationale for C++/CLI
Bronek Kozicki <brok@[  2006-02-19 10:22:55 
Re: A Design Rationale for C++/CLI
"Dilip" <rdi  2006-02-20 18:46:36 
Re: A Design Rationale for C++/CLI
"Andrew Browne"  2006-02-22 16:21:21 

Post A Reply:
  Go here to Signup

AddThis Feed Button


About - Advertising - Contact - Frequently Asked Questions - Privacy Policy - Terms of Use - Signup

Contact
tan12V112 Wed Aug 20 4:41:13 CDT 2008.