|
![](/i/fill.gif) |
"scott" <sco### [at] scott com> wrote in message
news:4acf4330$1@news.povray.org...
> [...]
> One little niggle I had to start with was that when you define a class,
> you need to write the code for all the methods of that class in the
> definition too (in C++ I would usually put the actual method code in a
> separate file). [...]
In the .NET environment, you could do it that way by writing an interface,
then implementing the interface in a class definition. I wouldn't recommend
doing that just to make C# behave like C++, though. C# is great at what it
does, and C++ is great at what it does, but they're really two different
languages. C# is a front end for the .NET CLR, and is made so that C and C++
programmers have a familiar way in to that environment. C++ is for
programming down to the bare metal, and hopefully always will be.
I use .NET languages when I need to quickly make input modules. You still
can't beat C++ for performance, though. :)
Post a reply to this message
|
![](/i/fill.gif) |