Re: "pointers" in /clr
- From: "William DePalo [MVP VC++ ]" <willd.no.spam@xxxxxxxx>
- Date: Tue, 15 Nov 2005 23:14:37 -0500
"beginthreadex" <beginthreadex@xxxxxxxxxxx> wrote in message
news:eLzK8oi6FHA.476@xxxxxxxxxxxxxxxxxxxxxxx
> The frustrating part is that articles from Microsoft do not designate they
> are for managed code only.
Hmm.
What I agree is confusing is tagging everything with the .Net moniker. We
sometimes get questions here as to whether Visual Studio .Net includes a
"real" C++ compiler. The truth is that it in effect includes four
compilers - C, C++ for native applications and Managed C++ and C++/CLI for
managed code.
On the other hand, it is hard to imagine an article on the new syntax not
being couched in .Net terms.
> Persons that have been developing in VC++ for many years might run into
> the
> same issues that I do with my teams. If MS knows that the classes are
> collected then the syntax should not matter.
They tried going down this path. We told them that we hated it. They
listened. In fact the point can be made that things are _less_ confusing
now: the new operator is a used to allocate and initialize native objects
while gcnew is used for managed objects. Here the departure from the norm
makes the intent crystal clear.
Regards,
Will
.
- References:
- "pointers" in /clr
- From: Peter Oliphant
- Re: "pointers" in /clr
- From: Nishant Sivakumar
- Re: "pointers" in /clr
- From: beginthreadex
- Re: "pointers" in /clr
- From: William DePalo [MVP VC++ ]
- Re: "pointers" in /clr
- From: beginthreadex
- "pointers" in /clr
- Prev by Date: re: Where is the STL.NET?
- Next by Date: Form KeyDown Problem
- Previous by thread: Re: "pointers" in /clr
- Next by thread: Re: "pointers" in /clr
- Index(es):
Relevant Pages
|