Linked by Thom Holwerda on Sat 26th Nov 2005 17:02 UTC, submitted by Megatux
Gnome "I followed the debate about a successor for the C/C++ combination as the primary language for developing the GNOME core desktop platform very closely last month. There has been discussion about a number of options. What I would like to do on this page is give an overview how a probably less well-known language might be a viable compromise as a C/C++ successor. This language is called Eiffel and exists for over a decade. Eiffel takes the principle of Object-Oriented programming to its extremes and, as a consequence, is a very easy to learn language."
Thread beginning with comment 65188
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:

When we are assimilated in the borg collective then we can all be perfectly efficient and work the same, collectively.

Judging by the amount of bad C/C++ code out there, I'd say that the borg collective is alive and well. My money's on the fellas using languages that force them to plan for bugs that are avoiding things like rocket crashes.

But, if you want to write fast, sloppy code without planning too much or thinking too much about it, then by all means use C/C++ or your favorite...

NOTE: My problem with Eiffel is that the compiler writers seem to fork their code on occasion, making past code unuseable. I had a system that I was planning to expand, but SmartEiffel forked me; my code would no longer compile. Time to look around...

Reply Parent Score: 2

ma_d Member since:

How is not wanting to get forced into a construct synonymous with wanting to write quick sloppy code.

There's more than one way to write well finished code (I'm not gonna back that up, it's pretty much a universal constant in life that there's always more than one way to do things).

Frankly, what you just said was FUD: If we keep using languages which don't force this or that we'll have sloppy bad code forever. The quality of software in general has increased vastly over the last 10 years, and the 10 years before that, and the 10 years before that.
The sky is not falling folks. The worst thing that using a dated language is going to do is slow us down. Software isn't going to suddenly become horridly broken.
It's no excuse to stick with c forever. But I'm not about to jump into languages which say "thou shalt use OO, or I wilt error" or languages which say "if thou dost not give me io ranges I wilt cry and kill thine first born!"
It sounds like that is all optional in Eiffel, as it should be. It's likely an effective tool, for some more than others. But if you force it, it's just going to make for a bunch of angry programmers who hate their jobs because all they do is fill out function i/o range and exception reports (think TPS reports).

You'll never finish a c project if you don't think it through. And you won't even get a c++ project to compile without thinking it through.

PS: Did they give you a tutorial on updating. This sort of thing seems to be fairly common in high level languages; and they'll usually give you a list of deprecated junk... I'd imagine porting your code shouldn't take too awful long. That's the nature of languages that do more for you; they change more.

Reply Parent Score: 1

Member since:

"But, if you want to write fast, sloppy code without planning too much or thinking too much about it, then by all means use C/C++ or your favorite... "

Somehow I get the impression that the poster would have problems fitting into the XP methadology. Too "borg-like". Oh well, as they say on Slashdot. ADAPT OR DIE!.

Reply Parent Score: 0