Slashdot Mirror

← Back to Stories (view on slashdot.org)

EiffelStudio 5.2 For Linux Released

Posted by timothy on from the does-it-tower dept.

sniesen writes "ISE finally released EiffelStudio 5.2 for Linux (and other UNIXes) today. There's free non-commercial editions available for both Windows and Linux. It's good to see that the best O-O language available still strives quite a bit."

4 of 43 comments (clear)

  1. Great by ajw1976 · · Score: 1, Interesting

    A good programming language that no one cares about or uses.

    --
    1. Bad signature
    2. ?????
    3. Profit
    1. Re:Great by 0x0d0a · · Score: 3, Interesting

      Yeah, I've noticed that. Seems like all the job reqs these days include Perl, from soft. dev to sysadmining to computer engineering. Now, I know Perl (well, enough of a subset to comfortably code in), but I hate to think of the masses of unmaintainable code being written.

      --
      May we never see th
  2. Re:What the hell is it? by DJSpray · · Score: 3, Interesting

    Both implementations look very promising, but there's always a problem. I've been aware of Eiffel for at least 9 years, but have never been able to use it for a real project, and, unfortunately, it looks like I will still not be able to.

    The barriers now are the cost of the commercial IDE, which is pretty far out-of-line (but if that was the only barrier, it would not be enough to keep me from using it). My co-developer is a Microsoft user and is very pleased by the idea of being able to use his Visual Studio environment. So they've got at least one developer here interested that way.

    The more important barrier is lack of a ready-to-roll set of tools for MacOS X. Normally I'd not be averse to becoming beta testers, but we can't bet this project on the quality of a beta.

    I'll check back in another 9 years, I guess.

    It's these "minor" practical matters more than anything else which means I'm still using the living hell that is C++ for my bread-and-butter work.

    Paul R. Potts

  3. Threads, GC and philosophy... by thallgren · · Score: 2, Interesting

    I never understood why they limit objects created on one thread to that thread. It's incredibly common to have a producer thread that enqueues objects for another thread to consume.

    But in the Eiffel world, they talk about sending data over tcp/ip to solve this.

    Does anyone know the reasons? I understand that the GC may be a lot simpler to implement, but this can't surely be the actual reason, can it?

    Regards, Tommy