Locations of open-source versions of EiffelStudio and libraries

[Eiffel Users]

For EiffelStudio:

The GPL-licensed source code, now updated to version 19.12 , is available in the following two locations:

- Subversion repository at
                  https://svn.eiffel.com/eiffelstudio-public

- Github mirror at
                  https://github.com/eiffelsoftware/eiffelstudio
with the same content as the previous one but Trunk only (no branches).

For the libraries:
The source of the Eiffel libraries (EiffelBase, EiffelVisionetc.) are available on a mirror site:
                  https://github.com/eiffelsoftware/libraries

The content always reflects the latest version, updated daily.

[Vivien Moreau]

Hi everyone,

Le 16/01/2021 à 14:02, Eiffel Users a écrit :
> The GPL-licensed source code, now updated to version 19.12 , is

> available in the following two locations [...]

I want to thank EiffelSoftware for this and also use the occasion to say
hello as this is my first message here, although I have been lurking for
2 years now.

I first became aware of Eiffel in 2018. I had heard of it before but
didn't see its advantages and thought it was still exclusively under a
proprietary license. After reading Hillel Wayne's post [1] on contracts
and after some adventures with D, I became attracted by the consistency
of Eiffel and its promises and found out EiffelStudio was free and
open-source! I started reading OOSC2, Touch of Class and even some books
from the 90's, (re)learning OOP along the way.

Right when I was thinking of committing more of my time writing
(hobbyist) software in Eiffel, two things happened: an account was now
required to use EiffelStudio and affordable licenses were made
available. While I was glad to be able to contribute with money, I was
also afraid that the plan was to stop releasing EiffelStudio under GPLv2
and decided to wait a bit to see the evolution of the situation. [2]


So I am very glad about this new arrangement which I hope will be a good
trade off between open-source and business for everybody involved. I
bought a license and expect to be posting here more often with questions
and eventually answers!

Have a nice day and happy Eiffeling!

[1] https://www.hillelwayne.com/post/contracts/

[2] no "whining" or intent of disrespecting God here, but mostly the
practical observation that while I could pay for my license, my chances
of sharing and reusing code and attracting other people to Eiffel would
be greatly reduced.

--
Vivien Moreau (jmiven)

[Larry Rix]

Vivien!

Thank you for an excellent discourse of your thoughts. Moreover—thank you for being a bright and wonderful lady willing to wade in with the "boys club" and show us that women make fantastic engineers! Nearly every female engineer I have met has been an outstanding individual and consummate professional! So, I applaud you!

My hope is that the on-going GPL version will continue to serve the entire world well as it has for many years!

In case you missed it—I was just the proud recipient of a self-made design flaw (bug) that was revealed by way of Design by Contract. When such things happen, it provides a huge reinforcement of not only the power of Design by Contract, but the extremely well thought out way that it is implemented in Eiffel through Eiffel Studio! As you can imagine, catching a "design flaw" is actually a step above the catching of a simple bug. It means that the reach of Design by Contract extends into a much more subtle and higher realm of software engineering.

Finally—I also applaud you for actually taking the time to read, digest, and utilize OOSC-2 and Touch of Class! Both of these books are seminal works. The only other written work I have found to be of equal importance is the Eiffel ECMA standard. From what I know, Bertrand is working on an updated and revised version of that to bring the specification up-to-date with all of the changes to Eiffel since that spec was written so many years ago. Nevertheless—it is an outstanding tool for understanding the Eiffel compiler and learning to "think-like-your-compiler", which is an excellent way to become an excellent Eiffel programmer.

Kindest regards,

Larry Rix

[Vivien Moreau]

Le 21/01/2021 à 21:11, Larry Rix a écrit :
> Thank you for an excellent discourse of your thoughts. Moreover—thank
> you for being a bright and wonderful lady willing to wade in with the
> "boys club" and show us that women make fantastic engineers! Nearly
> every female engineer I have met has been an outstanding individual and
> consummate professional! So, I applaud you!

Hah! Well I appreciate the sentiment, but I'm sorry to disappoint: in
France Vivien is actually a name given to boys, not girls!

> In case you missed it—I was just the proud recipient of a self-made
> design flaw (bug) that was revealed by way of Design by Contract. When
> such things happen, it provides a huge reinforcement of not only the
> power of Design by Contract, but the extremely well thought out way that
> it is implemented in Eiffel through Eiffel Studio! As you can imagine,
> catching a "design flaw" is actually a step above the catching of a
> simple bug. It means that the reach of Design by Contract extends into a
> much more subtle and higher realm of software engineering.

I still lack real experience of DbC (in actual projects), but I can
imagine, sure.

> Finally—I also applaud you for actually taking the time to read, digest,
> and utilize OOSC-2 and Touch of Class! Both of these books are seminal
> works. The only other written work I have found to be of equal
> importance is the Eiffel ECMA standard. From what I know, Bertrand is
> working on an updated and revised version of that to bring the
> specification up-to-date with all of the changes to Eiffel since that
> spec was written so many years ago. Nevertheless—it is an outstanding
> tool for understanding the Eiffel compiler and learning to
> "think-like-your-compiler", which is an excellent way to become an
> excellent Eiffel programmer.

Thanks for the suggestion. I read a bit through it and it does seem to
be the kind of standard useful to the programmer and not just the
compiler implementer. I can definitely see myself using it.

--
Vivien Moreau (jmiven)

[Larry Rix]

LOL -- my mistake then. My grandmothers name was Vivien and I've not heard of being used for boys/men before. Nevertheless--glad you are aboard!

[Larry Rix]

Also--I await Bertrand's revised version of the ECMA standard with great anticipation.

[Ulrich Windl]

>>> Larry Rix <lar...@moonshotsoftware.com> schrieb am 22.01.2021 um 00:49 in
Nachricht
<CAJ7KgmD5y0JqDuNUmO1H1MXK...@mail.gmail.com>:

> Also--I await Bertrand's revised version of the ECMA standard with great
> anticipation.

Makes me wonder: Is there a "language design group" that discusses new features heavily before they get implemented in Eiffel Studio or get documented in some draft standard?

(I'm in some working group of a different kind, and the discussions there are occasionally "quite heavy", but I still think discussing before implementing is a good thing)

Regards,
Ulrich