Linked by Thom Holwerda on Sat 26th Nov 2005 17:02 UTC, submitted by Megatux
Permalink for comment 65074
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
---
Here's a little definition of Eiffel for you.
Think about it before you go blurting out you lack of knowledge about Eiffel:
Think of Eiffel as a Java (OOP, Garbage collection, documentation) but *C* fast. Gcc fast.
Code in Eiffel is written with Design by Contract. This is a vaccine against bugs.
This is Eiffel. It's been around for years.
And the only thing stopping it from being used are a couple of non-techical factors:
1) Disinformation
2) Prejudice
3) Lack of marketing (not Sun, not Microsoft, not IBM (read linux))
4) Because there were few Eiffel vendors, all quite content making good money to a selected clientelle. But there's SmartEiffel now.
The problem with C/C++ ???!! What ??!! Don't you know ??! Are you aware of the hundreds of exploits because of unsafety ???!!
Microsoft is moving away from C++ (in fact, Microsoft Research has hired some of the very best people from industry and academia. Already they have formal verification of device drivers). Will we not ? We want to be the community that gets listed on a daily basis on security lists because of buffer overflows ?!
My guess: the free software community will reject Eiffel on the basis of ignorance. Why ? Simply because not too many coders are willing to stop and actually /think/ about the piece of code they're writing (the "release early, release often" Got root?
Eiffel grants you no excuse for not using a language with garbage collector. There's no performance trade off. Even C++ freaks will eventually resort to garbage collector in a sufficiently large program.
See these two free books on techniques of programming:
http://www.eng.unt.edu/~ian/books/poa.html
http://www.cs.toronto.edu/~hehner/aPToP/