Mailinglist Archive: opensuse (4570 mails)
| < Previous | Next > |
Re: [SLE] Clearing up the FUD on CLI/Mono
- From: "Steven T. Hatton" <hattons@xxxxxxxxxxxxxxxxxx>
- Date: Sun, 13 Nov 2005 01:18:08 +0000 (UTC)
- Message-id: <200511122017.50068.hattons@xxxxxxxxxxxxxxxxxx>
On Saturday 12 November 2005 07:22 pm, Anders Johansson wrote:
> On Sunday 13 November 2005 01:01, Steven T. Hatton wrote:
> > On Saturday 12 November 2005 03:00 pm, Steve Graegert wrote:
> > > What would be the rationale behind using C++ in .NET?
> >
> > C++/CLI is an ECMA standardization effort.
>
> Don't stare yourself blind at standards. The main issue is patents
>
> FWIW, I consider c++ to be one of the worst languages ever to not be
> designed. java in many ways is what C++ wanted to be, and with gcj's
> ability to compile to native code, it isn't that bad at performance
I'll have to disagree with you. There are a few C features of C++ that
Stroustrup says he would rather have foregone, but he states very clearly
that Java is _not_ what he would have designed had it not been for C
compatability. C++ is a very carefully designed language. It is not as easy
to use as Java for a person who has not carefully studied it, but when you do
learn C++, you can often express things very concisely and elegantly.
Java's answer to memory leaks is garbage collection. C++'s answer is RAII.
RAII requires you to think about what you are doing at a more fundamental
level. That may take more work, but the end result is typically much better
design.
You may want to look at _The Design and Evolution of C++_, by Bjarne
Stroustrup.
Steven
> On Sunday 13 November 2005 01:01, Steven T. Hatton wrote:
> > On Saturday 12 November 2005 03:00 pm, Steve Graegert wrote:
> > > What would be the rationale behind using C++ in .NET?
> >
> > C++/CLI is an ECMA standardization effort.
>
> Don't stare yourself blind at standards. The main issue is patents
>
> FWIW, I consider c++ to be one of the worst languages ever to not be
> designed. java in many ways is what C++ wanted to be, and with gcj's
> ability to compile to native code, it isn't that bad at performance
I'll have to disagree with you. There are a few C features of C++ that
Stroustrup says he would rather have foregone, but he states very clearly
that Java is _not_ what he would have designed had it not been for C
compatability. C++ is a very carefully designed language. It is not as easy
to use as Java for a person who has not carefully studied it, but when you do
learn C++, you can often express things very concisely and elegantly.
Java's answer to memory leaks is garbage collection. C++'s answer is RAII.
RAII requires you to think about what you are doing at a more fundamental
level. That may take more work, but the end result is typically much better
design.
You may want to look at _The Design and Evolution of C++_, by Bjarne
Stroustrup.
Steven
| < Previous | Next > |