We are pleased to announce the availability of EiffelStudio 20.11.
Try it right now! All the download sites have been updated.
The highlights are:
Let's remind the main highlights of previous EiffelStudio 20.05 :
See the release notes for details.
Happy Eiffeling,
-- The Eiffel Software Team
The cited addition going back to 20.05
> Improved support for Unicode: in the search tools, in code completion to insert Unicode symbols
includes completion support in EiffelStudio making it easy to use Unicode quantifier expressions such as
if ∃ c: your_string ¦ c.is_upper then …
A blog post I just wrote, https://bertrandmeyer.com/2020/12/24/right-forms-expression/, gives more details.
-- Bertrand Meyer
--
You received this message because you are subscribed to the Google Groups "Eiffel Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to eiffel-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/eiffel-users/f12176b3-8d8f-4bb5-9485-8c12d12ae240n%40googlegroups.com.
Yes, it’s a broken bar, because the normal bar would create a syntactical conflict since it is allowed in free operators, where it is actually used fairly often in practice. We did look for a way to allow it anyway, through ad hoc techniques for syntactical disambiguation, but did not find an obvious solution. The expectation is that most of the time the broken bar will be generated automatically through completion, so this shouldn’t be too much of a burden.
The issue here is backward compatibility == we do not want to break existing code.
-- BM
--
You received this message because you are subscribed to the Google Groups "Eiffel Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to eiffel-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/eiffel-users/c3f81d9d-a8fb-8504-92b4-a1c5945b5633%40gmx.net.
To view this discussion on the web visit https://groups.google.com/d/msgid/eiffel-users/044701d6d9ff%249c679410%24d536bc30%24%40inf.ethz.ch.
Sorry, it was meant as two hyphens approximating an em-dash “—“, my finger slipped to the right.
-- BM
To view this discussion on the web visit https://groups.google.com/d/msgid/eiffel-users/CAN%3DG_amWC%3DEgRaoX1oT%2BhWbUdUhd7G0B%3Dtrg15%3DdLoaV%2BKbZ%3DQ%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "Eiffel Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to eiffel-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/eiffel-users/7f8c0ef2-4c6e-4955-acc2-2c365164f3aan%40googlegroups.com.
Good day,
By looking at the 20.11 release of EiffelStudio, I just notice that the GPL LICENCE files of the 19.05 has been replaced by a proprietary EULA. Being a free software advocate, using Free Software is extremely important for me. So is someone can confirm that Eiffel Studio still has an Open-source license (like it is still indicated there: https://www.eiffel.com/eiffelstudio/licensing/) or is Eiffel now only behind a proprietary EULA?
Thanks,
Louis M
--
You received this message because you are subscribed to the Google Groups "Eiffel Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to eiffel-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/eiffel-users/d1450bb3-e183-4602-b448-f64bbda3be16n%40googlegroups.com.
Thanks. This is reassuring. I was wondering because in the past, both version was released at the same times.
Louis M
To view this discussion on the web visit https://groups.google.com/d/msgid/eiffel-users/3709c2f2-5973-4b95-82c9-bbb168690616n%40googlegroups.com.
Dear Ulrich,
> After browsing the Unicode tables a bit, I wonder about these operators:
> Should they all be implemented in the appropriate classes?:
∃∀∄∈∉∋∌∌⊂⊃⊄⊅⊆⊇⊈⊉⊊⊋
Indeed, class SUBSET of EiffelBase now has the basic membership and subset/superset operators as operator aliases. Not all of the above but the most common ones.
Also membership, in SET, but only ∋, as an operator alias for `has'. At the moment ∈ is not possible (see a discussion started by Jonathan Ostroff some time ago).
(The problem with ∈ is that in the simplest approach it would have to be in ANY, but that class should not depend on non-kernel classes such as SET.)
Union and intersection symbols È and Ç are not present because the corresponding features in SUBSET are procedures (used as e.g. a.merge (b), meaning a := a È b), I guess for performance reasons. Actually the function versions should be added (if only for purposes of writing contracts, but also for people preferring a functional style of programming), with the appropriate Unicode aliases.
∃ and ∀ are not operators (in the sense of denoting features of some class), but part of the syntax.
With best regards,
-- Bertrand Meyer
To view this discussion on the web visit https://groups.google.com/d/msgid/eiffel-users/5FF30946020000A10003DEF5%40gwsmtp.uni-regensburg.de.