c# lesson for c++ developers

[Matter Paneer]

I was sitting on my porch reading 'c# Class Design' from WROX press and i
thought this paragraph was interesting:

______
Where reference types are concerned, C++ developers will need to get used to
not thinking in terms of pointers. Although this is more-or-less what
happens behind the scenes, the CRL moves objects around on the managed heap
and adjusts references on the fly while the application is running. SInce
we don't notice this at run time and it's no obvious from the source code,
it confuses matters if you mentally try to tranlate between c# and c++ as
you write.
_____
This to me shows what a radical break there is between c++ and c# and how
being a c++ *guru* can be a real detriment to learning c#.

--
W '04 <:> Open

[Bob Grommes]

'Tis true.

It isn't just that some things in C++ don't map directly to C# either; C/C++
coders tend to think at a lower level, "closer to the metal". This is great
for writing device drivers or real-time interaction, but isn't terribly
appropriate for producing line-of-business apps. C# very strongly
discourages the use of pointers and doesn't support macros, for example,
because such things are more evil than good for the kinds of applications C#
is optimized to address.

--Bob

"Matter Paneer" <ja*****@earthlink.net> wrote in message
news:La****************@newsread2.news.pas.earthli nk.net...

I was sitting on my porch reading 'c# Class Design' from WROX press and i
thought this paragraph was interesting:

______
Where reference types are concerned, C++ developers will need to get used to not thinking in terms of pointers. Although this is more-or-less what
happens behind the scenes, the CRL moves objects around on the managed heap and adjusts references on the fly while the application is running. SInce we don't notice this at run time and it's no obvious from the source code,
it confuses matters if you mentally try to tranlate between c# and c++ as
you write.
_____
This to me shows what a radical break there is between c++ and c# and how
being a c++ *guru* can be a real detriment to learning c#.

[The Real Andy]

On Sun, 25 Apr 2004 22:09:48 -0700, "Bob Grommes" <bo*@bobgrommes.com>
wrote:

'Tis true.

It isn't just that some things in C++ don't map directly to C# either; C/C++
coders tend to think at a lower level, "closer to the metal". This is great
for writing device drivers or real-time interaction, but isn't terribly
appropriate for producing line-of-business apps. C# very strongly
discourages the use of pointers and doesn't support macros, for example,
because such things are more evil than good for the kinds of applications C#
is optimized to address.

--Bob

Try coming from embedded c and c++! My business partner is always
convincing me that I no longer need to optimise every single piece of
code for that extra 1uS performance!