Fifth International Eiffel Programming Contest 21
Berend de Boer writes "After a two year hiatus, the Eiffel Struggle is organized again. This series of contests started in 1997. To enter, people have to submit an Eiffel application or library. Closing date is October 31. Entries are judged according to 12 criteria. Entries are ranked into gold, silver and bronze. In order of rank, winners will be able to pick one of the prizes ."
Nice Prizes (Score:2, Funny)
Eiffel.NET (Score:3, Interesting)
Re:Eiffel.NET (Score:3, Insightful)
Re:Eiffel.NET (Score:3, Funny)
Re:Eiffel.NET (Score:2)
Re:Eiffel.NET (Score:2, Funny)
And does the popularity of the language indicates how popular correctness and reuse are with the programming population?
Re:Eiffel.NET (Score:3, Interesting)
Agreed. Correctness is not something programmers are interested in, it seems. Why else are people still using languages that cannot assure that you do not compare metres and feet [space.com]? Why are people still using languages that cannot assure you don't have buffer overflows?
Testing doesn't help, because your tests can have bugs too and are probably incomplete. It's gives a lot of peace to the mind if you hit the compile button in Eiffel and it compiles successfully.
That does not imply Eiffel is the end of the
Re:Eiffel.NET (Score:1, Informative)
Re:Eiffel.NET (Score:4, Interesting)
nearly everyone who took the class walked away with a bad experience. Why? Because of the documentation.
If you want eiffel to be more widely used, I highly suggest someone writing some decent documentation. Perhaps a searchable database of object, along with description of what the objects do and what their functions do.
That was my only real complaint. the current documentation sucks.
Re:Eiffel.NET (Score:1)
Because Eiffel has put emphasis on documentation _in_ the source code long before there was JavaDoc (for example). The language reference book (ETL) even defines certain views that help you understand how to use a class (flat, short, flat/short etc).
And all Eiffel compilers I know support those tools. Even the non graphical SmartEiffel comes with command line tools to s
Re:Eiffel.NET (Score:2)
keep in mind that our professor was a complete bitch, and had a superiority complex.
she needed a leg up on us to answer our questions, so it's possible she didn't tell us about any internal documentation because she would lose her position of power(yes, this sound paranoid, but we learned to expect this kind of behavior from her.)
I found a couple of the source files for classes while browsing online, but they were severely lacking in description of what the functions DID.
Re:Eiffel.NET (Score:1)
localhost% short dictionary
Or maybe I'd rather look up the array class.
localhost% short array
Re:Eiffel.NET (Score:2, Informative)
http://msdn.microsoft.com/library/techart/PDC_eif
Hope that helps.
Backup servers (Score:4, Informative)
In case the NICE [eiffel-nice.org] tiny solaris server is killed, here some backup servers:
http://www.berenddeboer.net/nice/eiffelstruggle/20 03/ [berenddeboer.net]
And the Google cache [google.com].
.eiffel links at cetus (Score:4, Informative)
Eiffel IRC channel at irc.debian.org (Score:3, Informative)