.NET (managed code) confusion

[Z.K.]

I am curious as to why this code works:

Form2 ^OC = gcnew Form2();
OC->Text = "Child";
OC->MdiParent = this;
OC->Show();

and this does not:

Form2 *OC = new Form2();
OC->Text = "Child";
OC->MdiParent = this;
OC->Show();
I have looked through all my .NET books about managed code and I can not
find any reference to using gcnew or the '^' which appears to be a
pointer notation. I am using the new Visual Studio 2005 if that
matters. I was wondering if someone could clear up my confusion.

Z.K.

[SvenC]

Z.K. wrote:

I am curious as to why this code works:

Form2 ^OC = gcnew Form2();
OC->Text = "Child";
OC->MdiParent = this;
OC->Show();

The above is the new C++/CLI syntax (default in VC++ 2005)

and this does not:

Form2 *OC = new Form2();
OC->Text = "Child";
OC->MdiParent = this;
OC->Show();

This is the old managed C++ syntax of VC++ 2003

--
SvenC

[Ben Voigt [C++ MVP]]

"SvenC" <Sv***@community.nospamwrote in message
news:67**********************************@microsof t.com...

Z.K. wrote:

>I am curious as to why this code works:

Form2 ^OC = gcnew Form2();
OC->Text = "Child";
OC->MdiParent = this;
OC->Show();

The above is the new C++/CLI syntax (default in VC++ 2005)

>and this does not:

Form2 *OC = new Form2();
OC->Text = "Child";
OC->MdiParent = this;
OC->Show();

This is the old managed C++ syntax of VC++ 2003

Which had all kinds of problems, including silently passing unpinned
pointers to native code and startup deadlock.

Use the C++/CLI syntax exclusively.

A lot of authors, caring about profit and not correctness, were racing to
get their books out first and didn't care to mention all the reasons Managed
Extensions shouldn't be used. They couldn't have had a good understanding
of the material. Anyone who tried to sell a "Managed C++" book using VC2003
instead of an article "Why Managed C++ isn't ready for the real-world" is a
profiteer, not a programmer, and you shouldn't buy any books by that author
ever again.

C++/CLI has finally existed long enough for some published books to be
available. I don't have it myself, but Nish's book is probably quite good
http://voidnish.com/NishBooks.aspx. He's another MVP and seems to know his
stuff.

[William DePalo [MVP VC++]]

"Ben Voigt [C++ MVP]" <rb*@nospam.nospamwrote in message
news:eU**************@TK2MSFTNGP02.phx.gbl...

Anyone who tried to sell a "Managed C++" book using VC2003 instead of an
article "Why Managed C++ isn't ready for the real-world" is a profiteer,
not a programmer, and you shouldn't buy any books by that author ever
again.

You mean like Siva Challa and Artur Laksberg - both on the compiler team at
MS - who wrote this one?:

http://www.amazon.com/Essential-Guid.../dp/1893115283

Theirs is a _good_ book.

While it is true that the language had problems, four years ago it was just
about the only option if one needed to straddle the fence between managed
and native development with C++.

C++/CLI is better to be sure but MC++ is far from unusable.

Regards,
Will

[Ben Voigt [C++ MVP]]

"William DePalo [MVP VC++]" <wi***********@mvps.orgwrote in message
news:e7**************@TK2MSFTNGP04.phx.gbl...

"Ben Voigt [C++ MVP]" <rb*@nospam.nospamwrote in message
news:eU**************@TK2MSFTNGP02.phx.gbl...

>Anyone who tried to sell a "Managed C++" book using VC2003 instead of an
article "Why Managed C++ isn't ready for the real-world" is a profiteer,
not a programmer, and you shouldn't buy any books by that author ever
again.

You mean like Siva Challa and Artur Laksberg - both on the compiler team
at MS - who wrote this one?:

http://www.amazon.com/Essential-Guid.../dp/1893115283

Theirs is a _good_ book.

Did they also clearly state the problems with the implementation? If not,
then it fails to meet my requirements.