[[Category:Releases]]__NOTOC__{{ReleaseHistoryHeader}}

= EiffelStudio 16.05 Releases=

Beta download: https://ftp.eiffel.com/pub/beta/16.05/

==16.05.9.8969 (July 8th 2016)==

===New features===
===Improvements===
===Feature removed===
===Bug fixes===
*EiffelBuild: Fixed a bug causing incompletely initialized application and environment objects to be used when showing a window in a project generated by EiffelBuild.
*library (Vision): bug#19241 - Fixed a non-critical bug in the feature <e>{EV_DIALOG_IMP_COMMON}.show</e> that might lead to infinite recursion on Windows, though the feature is never called because it is always redefined except in classes for modal dialogs where a different feature is used for display.
*library (Base): test#agent015 - Fixed a regression bug in .NET version of <e>ROUTINE</e> that may cause an incorrect result or an exception when calling <e>{ROUTINE}.valid_operands</e> on an agent with reference arguments or when invoking such an agent with preconditions turned on.
*library (Base): bug#19245 (test#directory002) - Fixed a bug preventing directory contents with non-ASCII entry names to be recursively deleted when using <e>{DIRECTORY}.recursive_delete</e>, <e>{DIRECTORY}.delete_content</e>, <e>{DIRECTORY}.recursive_delete_with_action</e> or <e>{DIRECTORY}.delete_contents_with_action</e>.
*library (Base): Fixed a bug when <e>{DIRECTORY}.delete_content_with_action</e> could call an action agent even when the argument <e>file_number</e> was not positive that should have prevented any agent calls.
*runtime: test#runtime020 - Fixed a bug that may cause a Windows application to crash when it attempts to use standard input/output.

===User changes===
*library (Base): test#directory002 - Avoided calls to an action agent from <e>{DIRECTORY}.delete_content_with_action</e> with the same arguments twice when processing nested directories.
*library (Base): test#directory002 - Changed <e>{DIRECTORY}.recursive_delete_with_action</e> to avoid calling an action agent when the argument <e>file_number</e> is not positive so that the behavior is similar to <e>{DIRECTORY}.delete_content_with_action</e>.

===Developer changes===

==16.05.9.8814==

===Improvements===
*compiler: Provided more details (such as option name, rule name, kind of syntax error) for errors in code analysis command-line options.
*compiler: Supported position-independent code analysis options (temporary retaining old code analysis options) that act like regular EiffelStudio command-line options:
<code>
-ca_class (-all | <class_name>)
-ca_default
-ca_rule <rule_name_with_optional_setting>
-ca_setting <preference_file_name>
</code>
*compiler: Relaxed void safety rules for local variables and <e>Result</e> by allowing assigning of detachable values to them even when their type is attached. The change allows dropping explicit detachable marks in local declarations and simplifying code that uses Result, e.g.,
<e>
foo: X
local
r: detachable X
do
r := something
if not attached r then
r := something_else_attached
end
Result := r
end
</e>
or
<e>
foo: X
do
if attached something as r then
Result := r
else
Result := something_else_attached
end
end
</e>
can now be rewritten as
<e>
foo: X
do
Result := something
if not attached Result then
Result := something_else_attached
end
end
</e>
The change does not allow previously void-unsafe code to be treated as void-safe, but may affect errors reported by the compiler, in particular:
# VEVI errors may be now reported as VUTA(2) when a local of an attached type is used as a target of call before it is attached.
# VEVI errors may be now reported as VJAR or VUAR when a local of an attached type is used as a source expression before it is attached.
# VJAR errors may now be reported as VUTA(2) when a local of an attached type is assigned a detachable value and is later used as a target of a call.
# VJAR errors may now be reported as VEVI when <e>Result</e> of an attached type is assigned a detachable value.
*compiler: Improved code generation for iterative form of loops in finalized mode by taking into account cursor types provided by iterable classes.
*compiler: Avoided object creation when accessing an attribute (usually <e>item</e>) on an expression of a basic type.
*compiler: Slightly improved performance of feature call on void target checks in finalized mode.
*compiler: Supported nested inlining of <e>{SPECIAL}.item</e> in finalized mode.
*library: Improved performance of iteration forms of loops for targets of the following classes: <e>ARRAY</e>, <e>ARRAYED_LIST</e>, <e>SPECIAL</e>, <e>READABLE_STRING_32</e>, <e>READABLE_STRING_8</e>.
*EiffelStudio: Improved reporting for errors in regular expressions used in include and exclude file rules in ECF by adding position information and providing error description all the time.

===Bug fixes===
*EiffelStudio: bug#19173 - Fixed a bug that caused an exception when requesting to generate documentation or XMI for a target with a library disabled by a condition.
*compiler: test#codeanalysis019 - Fixed a bug that caused duplicate reports for CA020 rule (unused assigned variable) inside one class or spurious reports for this rule on several classes.
*compiler: bug#18028 (test#final114), test#final123 - Fixed a bug that caused incorrect code generation when inlining <e>across</e> loops or <e>separate</e> instructions.
*compiler: test#scoop077 - Fixed a bug in applying SCOOP semantics rules and checking SCOOP validity rules for iteration forms of loops with a target of a separate type.
*EiffelStudio: bug#19212 - Fixed a bug that caused an exception when using metrics tool and affected [[EiffelStudio 15.12 Releases]].
*library: bug#19213 - Fixed a bug in an external signature of one of WEL features that might cause a crash when compiled with Gobo compiler.
*compiler: test#attach118 - Fixed a bug that might cause incorrect error reports for inherited code when target of reattachment involving conversion is of a detachable type.
*EiffelStudio: Added checks for validity of regular expressions used in include and exclude file rules specified in the project settings dialog with rejection of invalid regular expression using the corresponding error dialog to avoid a possibility to store ECF that cannot be retrieved.

===User changes===
*EiffelStudio: Changed order of processing of arguments taken from the command line and from the environment variable <code>ISE_EC_FLAGS</code>. Now arguments are first read from the environment variable and then from the command line.
*compiler: Marked old code analysis command-line options as obsolete.
*library: Changed interface and implementation of cursor classes used to implement <e>across</e> loops to get better performance.
*library: Added protection of window objects (of type <e>EV_WINDOW</e> and descendants) from garbage collection when there are no references to them or to objects holding such references and the associated windows become visible by using a feature <e>show</e> or its modifications (<e>show_modal_to_window</e> and <e>show_relative_to_window</e>) until the windows become hidden using <e>hide</e> or <e>destroy</e>. The protection should not affect any existing applications, but allows for easier window management in user's code especially in SCOOP mode.

EiffelStudio Releases

2016-07-09T07:16:10Z

Manus: Redirected page to EiffelStudio 16.05 Releases

#REDIRECT [[EiffelStudio 16.05 Releases]]

MediaWiki:Sidebar

2016-07-09T07:15:30Z

Manus:

Main Page

2016-07-09T07:14:30Z

Manus:

[[Category:General]]__NOTOC__
<h1 class="firstHeading">EiffelStudio Integrated Development Environment</h1>

[[Image:EiffelStudioScreenshot.png|thumb|250px|right|EiffelStudio IDE ([http://eiffel.com/products/studio/screenshots.html more screenshots]) ]]

Welcome to the central resource for EiffelStudio developers and contributors.
==News==
*''31st May 2016'': EiffelStudio [[EiffelStudio 16.05 Releases|16.05]] is available for download at https://www.eiffel.org/downloads
*''21st Dec 2015'': EiffelStudio [[EiffelStudio 15.12 Releases|15.12]] is available for download at https://www.eiffel.org/downloads

==Background==

EiffelStudio is an open-source IDE for the [http://en.wikipedia.org/wiki/Eiffel_programming_language Eiffel programming language]. [http://www.eiffel.com Eiffel Software] is the principal contributor and hosts the subversion repository. EiffelStudio is maintained and developed by Eiffel Software as well many contributors, including ETH Zurich.

EiffelStudio is a full-featured IDE offering the following features, many of them unique:

* Complete compiler for the Eiffel programming language, with Design By Contract (DBC) support and both high compile-time speed and high-performance executables, based on the Melting Ice Technology.
* Full portability (including graphics) across Windows, MacOS X, Linux, *BSD, Solaris and other operating systems
* Smart code editor
* Sophisticated multi-view browsing and viewing facilities
* Interactive debugger
* Graphical modeling tool for UML and BON with full roundtrip
* Refactoring support
* GUI development tool (EiffelBuild) and fully portable GUI library (EiffelVision)
* Many other libraries of reusable component.

The Eiffel compiler creates C code that is then handed to a standard C compiler. As a result, Eiffel programs have a run-time performance comparable to those directly written in C or C++, but with the benefits of an advanced object-oriented model and strong typing. EiffelStudio uses a highly efficient compacting garbage collector to free the developer from the burden of memory management.

<center>If you want to know more about the unique features of Eiffel and EiffelStudio, check out our [[Reasons for using Eiffel]] page.</center>

{|style="font-size:80%;" bgcolor=white|
{| cellspacing=8 width="100%"
|- valign="top"
|width="50%" bgcolor="#f6f9fb" style="border:1px solid #8f8f8f;padding:0 .5em .5em .5em;"|

== Getting Started ==

* [[Downloads]]
* [[EiffelStudio Releases|Changelog of current release (release branch)]]
* [http://docs.eiffel.com/book/eiffelstudio/software-installation-eiffelstudio Installing EiffelStudio]
* [[Compiling Hello World]]
|width="50%" bgcolor="#f6f9fb" style="border:1px solid #8f8f8f;padding:0 .5em .5em .5em;"|

== Working with EiffelStudio ==

* [[Frequently Asked Questions]]
* [[Eiffel Glossary]]
* [[Eiffel Compilation Explained]]
* [[EiffelStudio Wish List]]

|- valign="top"
|width="50%" bgcolor="#f6f9fb" style="border:1px solid #8f8f8f;padding:0 .5em .5em .5em;"|
== Contributing! ==

* [[:Category:Projects|How to contribute: the Projects page]]
* [[:Category:Testing|EiffelStudio testing process: you can participate!]]
* [[EiffelStudio 16.11 Releases|Changelog of latest development version, currently 16.11 (development trunk)]]
* [[Repository|Getting the source: Subversion repository]]
* [[Compiling EiffelStudio]]
* [[:Category:Tools|Developer's tools]]
* [[Language_Roadmap|Language roadmap]]
* [[Environment_Roadmap|Environment roadmap]]
* [[Design_and_coding_rules|Design and coding rules]]
|width="50%" bgcolor="#f6f9fb" style="border:1px solid #8f8f8f;padding:0 .5em .5em .5em;"|

== Community ==

* [https://www.eiffel.org Eiffel.org]
* [[Spread_the_word|Spread the word]]
* [[Eiffel Sites and Links]]
* [[Mailing Lists]]
* [[:Category:News|News]]
* Join us on gitter https://gitter.im/EiffelSoftware/EiffelStudio or through https://groups.eiffel.com/

|}

Environment Variables

2016-07-09T01:20:31Z

Manus:

[[:Category:EiffelStudio|EiffelStudio]]/Eiffel compiler utilizes a number of environment and other localized variables. This page is dedicated to those variables, how they are defined and what they mean.

{{Note|There is a special notion called "[[LinuxUnixLayout|Unix Layout]]" in regards to special builds of [[:Category:EiffelStudio|EiffelStudio]]. When using a [[LinuxUnixLayout|Unix layout]] '''no environment variables''' are used because of the fragmented distribution of installed files. For such layouts this page provides no contribution to understanding [[:Category:EiffelStudio|EiffelStudio]].

Unix layouts are used by package managers. See [[Linux Packages|here]] for supported package managers.}}

Unless otherwise stated, all the following environment variables are known by the Eiffel environment at run time.

== Core Variables ==
The core variables are the Eiffel compiler variables that absolutely must be defined for the [[:Category:EiffelStudio|EiffelStudio]]/Eiffel compiler to function. Without them the Eiffel environment has no idea where it is or what platform binaries to load.

* '''ISE_EIFFEL''': The holy grail of everything Eiffel, the only difference being is that this variable can be found! The value should point to the root of the [[:Category:EiffelStudio|EiffelStudio]]/Eiffel compiler installation.
* '''ISE_PLATFORM''': Represents the named platform on which the Eiffel environment is running. Below is a list of compatible platform names:
** freebsd-x86-64
** freebsd-x86
** irix-mips-64
** irix-mips
** linux-ppc
** linux-sparc
** linux-x86-64
** linux-x86
** macosx-x86
** macosx-x86-64
** openbsd-x86
** solaris-sparc-64
** solaris-sparc
** solaris-x86-64
** solaris-x86
** win64
** windows

=== Windows Variables ===
Under Microsoft's Windows an extra variable is required, dictating the external C compiler used by the Eiffel environment. Like the core variables, this variable must be defined in order for an Eiffel environment to run.

* '''ISE_C_COMPILER''': The noted and installed C compiler used by the Eiffel compiler to perform C/C++ compilation and to locate the compatible external libraries. Below is a list of compatible C compiler names:
** ''msc'': Any supported [[Installing Microsoft C compiler|Microsoft Visual C/C++]] compiler prior to Visual Studio C++ 2015.
** ''msc_vc140'': Visual Studio C++ 2015 or later.
** ''mingw'': The open source [http://www.mingw.org MinGW] C/C++ compiler, which at the time of writing is only available as a stable release for x86.
** ''bcb'': The Free Borland 5.5 C++ compiler which is now deprecated and should not be used.

== Optional Variables ==

In addition to the core variables, there are a number of optional variables that can be defined to replace predefined values set by the Eiffel environments.

* '''ISE_LIBRARY''': Points to an alternative location for library source files. By default this is automatically set by EiffelStudio to the same location as [[#Core Variables|ISE_EIFFEL]]. This is usually set explicitly when you are checking out the source code directly.

* '''ISE_PRECOMP''': The location of the Eiffel environment precompiled libraries. By default, this is automatically set by EiffelStudio to a user specific location which vary depending on the platform.

* '''ISE_CFLAGS''': C compilation flags that are passed to the C compiler. We recommend not using it but instead set the C compilation flags as part of your Eiffel Configuration File.

* '''ISE_SHAREDLIBS''': Some additional C/C++ libraries that are passed to the C/C++ linker. It can also be used to pass linker flags. Like '''ISE_CFLAGS''', we recommend not using it but instead set the C compilation flags as part of your Eiffel Configuration File.

* '''ISE_APP_DATA''': Location of the Eiffel environment configuration data, such as project settings data and session configuration data. This configuration data is hidden, managed by [[:Category:EiffelStudio|EiffelStudio]] and should not be manipulated manually.

* '''ISE_USER_FILES''': Points to the location of Eiffel environment user files like the default projects location, user [[Code Templates|code templates]] and Eiffel environment [[Replaceable_User_Files|Replaceable User Files]].

=== Auxiliary Variables ===
The following environment variables are defined when working with Eiffel environment sources. There is no internal knowledge of the following environment variables; they are used for configuration and compilation only.

* '''EIFFEL_SRC''': When working with the live Eiffel sources, EIFFEL_SRC points to the checked out /trunk/Src location.

* '''ISE_SRC''': This environment variable is used to point to the ISE internal repository containing non-GPL code. The variable points to /trunk/Src of the internal repository.

== Windows Localization ==
If you are running [[:Category:EiffelStudio|EiffelStudio]]/Eiffel compiler on a Microsoft Windows-based platform, environment variables may be localized to a specific version of the Eiffel compiler used to build the Eiffel application. This is extremely useful when using the Eiffel compiler with multiple source repositories, or when working on multiple branches or research versions. It is also used to allow the x86 and x64 versions of EiffelStudio to be installed side-by-side and even under the same location without bit-compatibility issues with the Eiffel compiler binaries or external C libraries.

{{Note|Environment variables defined for the user or system will override any localized variables.}}

[[:Category:EiffelStudio|EiffelStudio]] and the Eiffel compiler make use of localized variables to define information specific to each version of [[:Category:EiffelStudio|EiffelStudio]] installed. Those of you who have created environment variables used by the Eiffel environment, such as [[#Code Variables|ISE_EIFFEL]] or [[#Code Variables|ISE_PLATFORM]], will have seen an installer warning indicating the danger in defining those variables at that level.

So, on to localization and how it works.

=== The Windows Registry ===
People hate it, people love it, the Windows registry. It's nice to have uniform access to a collection of hives containing varying degrees of access. It's also where localized Eiffel variables can be manipulated, added or removed.

There are four places where local variables can be defined, each with their own degree of prioritization.

User variables, available only to the currently logged on user, are found under the key:

HKCU\Software\ISE\Eiffel_''YY.MM''\''app_name''

This is the very first place any Eiffel system will look for a local variable. For instance, [[:Category:EiffelStudio|EiffelStudio]] and the Eiffel compiler are bundled in the executable ''ec.exe''. For release YY.MM built with a YY.MM Eiffel compiler, ec.exe will first look for variables under:

HKCU\Software\ISE\Eiffel_YY.MM\ec

Failing to find any variable under this key, the system will default to looking at the compiled version key (the version of the Eiffel compiler the system was compiled with.) Using the same example, the following key will be examined:

HKCU\Software\ISE\Eiffel_YY.MM

Again failing to locate a matching variable name, the system will proceed to check the local machine hive, using the same rules as used by the current user hive.

HKLM\Software\ISE\Eiffel_''YY.MM''\''app_name''

Using the same example. the application specific key at will be searched next:

HKLM\Software\ISE\Eiffel_YY.MM\ec

And failing to find any matching variable the compiled version key will be the last place looked under:

HKLM\Software\ISE\Eiffel_YY.MM

To sum up, here is the list of searched locations. ordered by priority for retrieving, a variable; environment, local or otherwise:

# User environment variable table
# Machine environment variable table
# Current user registry hive under the Eiffel application specific key
# Current user registry hive under the Eiffel compiled version key
# Local machine registry hive under the Eiffel application specific key
# Local machine registry hive under the Eiffel compiled version key

EiffelOnMac

2016-05-14T05:03:44Z

Manus: /* Using Homebrew */

[[Category:EiffelStudio]]
[[Category:Macintosh]]

This page gives you an overview about how to get EiffelStudio running on your Mac (Mavericks or above).

==Requirements==

*'''X11 (XQuartz)''': install version 2.7.5 minimum from http://xquartz.macosforge.org.
*You will need to install '''Xcode''' from the App Store. After installing Xcode, make sure to install the command line tools by typing:
<pre>
xcode-select --install
</pre>
This will popup a dialog asking if you want to install the command line developer tools.

{{Note|If you have an OS older than 10.10 (e.g. 10.9.5) you might have a problem installing Xcode from the App Store. You can then go to https://developer.apple.com/downloads/ (Apple ID needed). Remember to install the command line tools.}}

{{Note| Advanced users may not need to install Xcode as long as you install the '''development tools'''. Even though you save in download time, you might waste a lot of time trying to fix missing dependencies. In other words, unless you are feeling adventurous, do install Xcode.}}

== Installation ==

=== Using MacPorts ===
MacPorts is a tool that allows you to use many Unix applications on the Mac. We have created a package in the MacPorts repository that allows you to to install Eiffel Studio with all dependencies in a convenient way. First, install [http://guide.macports.org/#installing MacPorts].

Now simply type (from a bash [http://guides.macrumors.com/Terminal terminal]):
<pre>
sudo port install eiffelstudio
</pre>
This will actually compile and install the whole EiffelStudio delivery. This takes about 15 minutes on a 2013 Mac.

When a new release of EiffelStudio becomes available, it may take some weeks before it's available from MacPorts. You can check by running this command:
<pre>
port info eiffelstudio
</pre>

Once the new release is available, you can upgrade like so:
<pre>
sudo port selfupdate
sudo port upgrade outdated
</pre>

=== Using Homebrew ===

{{Warning|As of 2015, the graphical version of EiffelStudio won't work in Homebrew due to a bug in the GTK package included in Homebrew. However all the command line tools will work.}}

A light-weight alternative to installing MacPorts is [https://github.com/Homebrew/homebrew/blob/master/share/doc/homebrew/Installation.md#installation Homebrew].
Once Homebrew is installed type the following commands to install EiffelStudio (from a bash [http://guides.macrumors.com/Terminal terminal]):

<pre>
brew update
brew install eiffelstudio
</pre>

=== Using binary packages ===

{{Warning|This method still requires an initial installation via MacPorts or Homebrew.}}

Download the latest .tar.bz2 package from the Eiffel Software site that matches MacPorts or Homebrew. Then follow the same [https://docs.eiffel.com/book/eiffelstudio/eiffelstudio-linux instructions as the Linux version] to setup the environment variables needed to run EiffelStudio. Keep the ISE_PLATFORM value to macosx-x86-64.

== Starting EiffelStudio installed via MacPorts ==

Simply navigate to /Applications/MacPorts/Eiffel''XX'' and double click the EiffelStudio icon.

Alternatively, you can also start EiffelStudio from the command line by entering the command 'estudio' or use the command-line eiffel compiler 'ec'.

==Hints==
* Pick and Drop works with Apple-key + mouse click.
* To set up the correct (default) browsers use "open" as your command-line browser in Tools>Preferences...
* The F10 and F11 debugging shortcuts conflict with the standard Exposé keys. Here are some workarounds:
** Use the toolbar instead.
** Reassign these shortcuts in EiffelStudio (Tools>Preferences).
** Reassign the Exposé keys in System Preferences.

== FAQ ==
=== How can I make EiffelStudio on the Mac look nicer? ===
* From macports, install the gtk2 (if not already installed) and gtk-chtheme packets. Then run gtk-chtheme and you get a nice GUI to choose your theme. Additional GTK themes can be put in /opt/local/share/themes/ (There a thousands of them on the web, for example here : [http://art.gnome.org/themes/gtk2 http://art.gnome.org/themes/gtk2])

=== Typing ec or estudio on the command line doesn't work ===
To run the '''ec''' compiler from your shell, set up variables similar to these (e.g. in ~/.profile):
<pre>
# Setting variables for EiffelStudio.
export ISE_EIFFEL=/Applications/MacPorts/Eiffel66
export ISE_PLATFORM=macosx-ppc (or macosx-x86)
export ISE_PROJECTS=$HOME
export ES_PATH=$ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin
export PATH=$ES_PATH:$PATH
</pre>

===The latest release of EiffelStudio isn't available yet via MacPorts===

If you want to upgrade to the latest release of EiffelStudio, but it isn't available yet via MacPorts, the easiest and quickest thing is to install from binary packages as noted above. Nonetheless, if you really want to install it via MacPorts, here's how.

MacPorts installs a particular version of EiffelStudio by following the rules defined in a '''Portfile'''. For example, http://trac.macports.org/browser/trunk/dports/lang/eiffelstudio71/Portfile is the Portfile for EiffelStudio 7.1. The person who maintains EiffelStudio for MacPorts has to write this file and upload it, but they might not have done so yet. You could make enquiries about when it will be available, but if you want to get the latest urgently it isn't hard to write your own Portfile and run it locally. Here's how.

http://guide.macports.org/#development.local-repositories explains how to do it.
# Go to https://sourceforge.net/projects/eiffelstudio/files and download the relevant PorterPackage file.
# Run '''openssl''' to find out the '''checksum''' of the PorterPackage file. E.g., for EiffelStudio 7.2 the command is '''openssl rmd160 ~/Downloads/PorterPackage_72_91284_gpl.tar'''.
# Open /opt/local/etc/macports/sources.conf in a text editor (with super user privileges). Insert a line as explained on http://guide.macports.org, e.g., file:///Applications/MacPorts/ports
# Create the Portfile in a text editor, e.g., file:///Applications/MacPorts/ports/lang/eiffelstudio72/Portfile
#* Copy the contents of the most recently available EiffelStudio Portfile (e.g., from http://trac.macports.org/browser/trunk/dports/lang/eiffelstudio71/Portfile) into your Portfile.
#* Correct the '''name''', '''minor_version''' and '''version'''.
#* Make sure that the '''distname''' will resolve to the current PorterPackage file name that you see on https://sourceforge.net/projects/eiffelstudio/files
#* Set the first '''checksums''' to the value that you got earlier from running openssl.
#* You've finished writing your Portfile. Save it!
# Go to the ports directory, e.g., cd /Applications/MacPorts/ports
# sudo portindex
# You should now be able to install in the usual way, e.g., sudo port install eiffelstudio72

EiffelOnMac

2016-05-14T05:02:38Z

Manus: /* Using Homebrew */

[[Category:EiffelStudio]]
[[Category:Macintosh]]

This page gives you an overview about how to get EiffelStudio running on your Mac (Mavericks or above).

==Requirements==

*'''X11 (XQuartz)''': install version 2.7.5 minimum from http://xquartz.macosforge.org.
*You will need to install '''Xcode''' from the App Store. After installing Xcode, make sure to install the command line tools by typing:
<pre>
xcode-select --install
</pre>
This will popup a dialog asking if you want to install the command line developer tools.

{{Note|If you have an OS older than 10.10 (e.g. 10.9.5) you might have a problem installing Xcode from the App Store. You can then go to https://developer.apple.com/downloads/ (Apple ID needed). Remember to install the command line tools.}}

{{Note| Advanced users may not need to install Xcode as long as you install the '''development tools'''. Even though you save in download time, you might waste a lot of time trying to fix missing dependencies. In other words, unless you are feeling adventurous, do install Xcode.}}

== Installation ==

=== Using MacPorts ===
MacPorts is a tool that allows you to use many Unix applications on the Mac. We have created a package in the MacPorts repository that allows you to to install Eiffel Studio with all dependencies in a convenient way. First, install [http://guide.macports.org/#installing MacPorts].

Now simply type (from a bash [http://guides.macrumors.com/Terminal terminal]):
<pre>
sudo port install eiffelstudio
</pre>
This will actually compile and install the whole EiffelStudio delivery. This takes about 15 minutes on a 2013 Mac.

When a new release of EiffelStudio becomes available, it may take some weeks before it's available from MacPorts. You can check by running this command:
<pre>
port info eiffelstudio
</pre>

Once the new release is available, you can upgrade like so:
<pre>
sudo port selfupdate
sudo port upgrade outdated
</pre>

=== Using Homebrew ===
A light-weight alternative to installing MacPorts is [https://github.com/Homebrew/homebrew/blob/master/share/doc/homebrew/Installation.md#installation Homebrew].
Once Homebrew is installed type the following commands to install EiffelStudio (from a bash [http://guides.macrumors.com/Terminal terminal]):

<pre>
brew update
brew install eiffelstudio
</pre>

=== Using binary packages ===

{{Warning|This method still requires an initial installation via MacPorts or Homebrew.}}

Download the latest .tar.bz2 package from the Eiffel Software site that matches MacPorts or Homebrew. Then follow the same [https://docs.eiffel.com/book/eiffelstudio/eiffelstudio-linux instructions as the Linux version] to setup the environment variables needed to run EiffelStudio. Keep the ISE_PLATFORM value to macosx-x86-64.

== Starting EiffelStudio installed via MacPorts ==

Simply navigate to /Applications/MacPorts/Eiffel''XX'' and double click the EiffelStudio icon.

Alternatively, you can also start EiffelStudio from the command line by entering the command 'estudio' or use the command-line eiffel compiler 'ec'.

==Hints==
* Pick and Drop works with Apple-key + mouse click.
* To set up the correct (default) browsers use "open" as your command-line browser in Tools>Preferences...
* The F10 and F11 debugging shortcuts conflict with the standard Exposé keys. Here are some workarounds:
** Use the toolbar instead.
** Reassign these shortcuts in EiffelStudio (Tools>Preferences).
** Reassign the Exposé keys in System Preferences.

== FAQ ==
=== How can I make EiffelStudio on the Mac look nicer? ===
* From macports, install the gtk2 (if not already installed) and gtk-chtheme packets. Then run gtk-chtheme and you get a nice GUI to choose your theme. Additional GTK themes can be put in /opt/local/share/themes/ (There a thousands of them on the web, for example here : [http://art.gnome.org/themes/gtk2 http://art.gnome.org/themes/gtk2])

=== Typing ec or estudio on the command line doesn't work ===
To run the '''ec''' compiler from your shell, set up variables similar to these (e.g. in ~/.profile):
<pre>
# Setting variables for EiffelStudio.
export ISE_EIFFEL=/Applications/MacPorts/Eiffel66
export ISE_PLATFORM=macosx-ppc (or macosx-x86)
export ISE_PROJECTS=$HOME
export ES_PATH=$ISE_EIFFEL/studio/spec/$ISE_PLATFORM/bin
export PATH=$ES_PATH:$PATH
</pre>

===The latest release of EiffelStudio isn't available yet via MacPorts===

If you want to upgrade to the latest release of EiffelStudio, but it isn't available yet via MacPorts, the easiest and quickest thing is to install from binary packages as noted above. Nonetheless, if you really want to install it via MacPorts, here's how.

MacPorts installs a particular version of EiffelStudio by following the rules defined in a '''Portfile'''. For example, http://trac.macports.org/browser/trunk/dports/lang/eiffelstudio71/Portfile is the Portfile for EiffelStudio 7.1. The person who maintains EiffelStudio for MacPorts has to write this file and upload it, but they might not have done so yet. You could make enquiries about when it will be available, but if you want to get the latest urgently it isn't hard to write your own Portfile and run it locally. Here's how.

http://guide.macports.org/#development.local-repositories explains how to do it.
# Go to https://sourceforge.net/projects/eiffelstudio/files and download the relevant PorterPackage file.
# Run '''openssl''' to find out the '''checksum''' of the PorterPackage file. E.g., for EiffelStudio 7.2 the command is '''openssl rmd160 ~/Downloads/PorterPackage_72_91284_gpl.tar'''.
# Open /opt/local/etc/macports/sources.conf in a text editor (with super user privileges). Insert a line as explained on http://guide.macports.org, e.g., file:///Applications/MacPorts/ports
# Create the Portfile in a text editor, e.g., file:///Applications/MacPorts/ports/lang/eiffelstudio72/Portfile
#* Copy the contents of the most recently available EiffelStudio Portfile (e.g., from http://trac.macports.org/browser/trunk/dports/lang/eiffelstudio71/Portfile) into your Portfile.
#* Correct the '''name''', '''minor_version''' and '''version'''.
#* Make sure that the '''distname''' will resolve to the current PorterPackage file name that you see on https://sourceforge.net/projects/eiffelstudio/files
#* Set the first '''checksums''' to the value that you got earlier from running openssl.
#* You've finished writing your Portfile. Save it!
# Go to the ports directory, e.g., cd /Applications/MacPorts/ports
# sudo portindex
# You should now be able to install in the usual way, e.g., sudo port install eiffelstudio72

Eiffel Breaking Changes

2016-01-29T12:31:09Z

Manus: /* Strings: remove implicit conversion STRING_32.as_string_8 */

[[Category:Compiler]]
[[Category:Eiffel Language]]
[[Category:Libraries]]
{{Warning|Article under development}}

=Introduction=
As of this writing, January 21st 2016, the Eiffel language has slowly evolved over the years and added numerous new facilities. Initially, the changes were done by Eiffel Software while maintaining backward compatibility. Then, a major work was done between 2001 and 2005 to standardize the language which became an ECMA standard in 2005 ([http://www.ecma-international.org/publications/standards/Ecma-367.htm ECMA-367]) and an ISO standard in 2006 ([http://www.iso.org/iso/catalogue_detail.htm?csnumber=42924 ISO/IEC 25436:2006]). That work established some constructs initially implemented in EiffelStudio and also introduced some new ones. Most of the changes introduced by the standardization have been implemented but there are quite a few remaining. In some cases, it is due to the ration cost/benefit of the implementation, in some others it is a breaking changes. In addition, since the standardization was completed, Eiffel Software kept adding new language features too.

This page is going to list all the changes that needs to be done by Eiffel Software to conform to the standard which cover both the language but also the library facilities required to support the language specification.

=Library changes=
==Strings==
===Before===
STRING maps to STRING_8
And we have STRING_32, IMMUTABLE_STRING_8 and IMMUTABLE_STRING_32

===After===
STRING should be the equivalent of what IMMUTABLE_STRING_32 was before.
STRING_8 should be the equivalent of what IMMUTABLE_STRING_8 was before.
MUTABLE_STRING_8 should be the equivalent of what STRING_8 was before.
MUTABLE_STRING_32 should be the equivalent of what STRING_32 was before.

===Rational===
When STRING_32 was added, we did not want to break existing code if it became the default. For example, many Eiffel libraries having a binding with C, could directly use an Eiffel STRING object as argument to a C routines. Of course this is very dangerous and we have changed this over the year to introduce safer mechanism (such as C_STRING).

Now the world is Unicode, not using a Unicode string by default does not make sense. On top of that, string instances are rarely modified and we have seen over the year many bugs because users have a tendency to forget this important fact. Which caused a lot of code to duplicate strings just to be sure, making the code less efficient. This is why we want to map STRING to IMMUTABLE_STRING_32.

The end benefit is that we would have cleaner string manipulations and more importantly much more efficient string operations (search, string sharing, traversals, ...)

===Issues===
A lot of code would not compile anymore by this change. Pretty much all libraries would have to be rewritten.

==Strings: remove implicit conversion from XXX_STRING_32 to XXX_STRING_8==
===Before===
XXX_STRING_32 implicitly converts to XXX_STRING_8.

===After===
No more XXX_STRING_32 to SSS_STRING_8 implicit conversion.

===Rationale===
This implicit conversion was great when the STRING_32 type was introduced in Eiffel and heavily used in EiffelVision2. It enabled existing code that was purely ASCII at the time to compile unchanged. The goal was always to remove that conversion as early as possible as it is a truncation which was ok as long as your were ASCII based.

Now this is a recipe for trouble to allow such an implicit conversion.

===Issues===
A lot of code would not compile anymore by this change if they use Unicode enabled libraries such as EiffelVision2 and still use STRING_8 in their code.

==Void-safe and invariant-safe copy==
===Before===
Whenever a user redefined copy, it was the assumption that argument's fields would be all set to their default value (case of '''copy''' called indirectly via '''twin''') or to some tangible value (normal case of doing '''x.copy (y)''').

===After===
Whenever a user redefines copy, all the fields are properly set to the fields of the original object which is either the object on which we call '''twin''' or the source being copied from.

===Rationale===
This makes the code fully void-safe as we will never try to access fields that are declared attached but actually Void.

This removes the need to disable invariant checking in the implementation of '''twin'''.

===Issues===
Because '''copy''' can be called directly or indirectly, we used to perform the following test on a field that was supposedly attached at runtime:

<e>
if field = Void then
-- Called from `twin`
...
else
-- Direct call to `copy'
...
end
</e>

This kind of code won't work anymore. Instead one has to do
<e>
if Current = other then
-- Called from `twin`
...
else
-- Direct call to `copy'
...
end
</e>

but this is not ideal since we cannot distinguish between <e>a.twin</e> from <e>a.copy (a)</e>. Since calling the later is very rare, the above solution is a good one overall.

==Restrict export to copy==
===Before===
You could duplicate objects as you wish.
===After===
You can only duplicate objects if they are marked as `copiable' or `duplicable'. So far there is no definite answer to allow this. What is being proposed is either one of the following:
# Define '''twin''', '''copy''', ... in ANY like today, but exported to NONE.
# Remove '''twin''', '''copy''', ... from ANY and add them to a new abstract class COPIABLE
The second solution is simple as at runtime we simply have to check for conformance to COPIABLE.
===Rationale===
If you duplicate an object graph that has some external memory reference, causing a duplication of the object holding that reference could cause a double-free of that external memory reference when Eiffel objects are disposed by the GC.

In addition, some objects are complicated to duplicate such as: Files, Windows, Widgets, databases connections,...

===Issues===
For client code, it should still compile as before. For user defined code that is known to allow copy/duplication, the code will have to be rewritten to allow copy/duplication.

==Change the type describing the dynamic type of objects==
===Before===
In non-void-safe mode and in void-safe mode, the dynamic type of an object was '''detachable X'''.
===After===
The dynamic type of an object would always be '''attached X'''.
===Rationale===
It is common sense that an object presence indicates implicitly that it is attached and it will simplify code that test for the type of an object. Currently one had to write:
<e>
if attached {TYPE [detachable X]} obj.generating_type then
</e>
when really it makes more sense to write:
<e>
if attached {TYPE [X]} obj.generating_type then
</e>
===Issues===
It was initially '''detachable X''' for reasons that are too complex and vague as of this writing (mostly related to backward compatibility, storable, reflection). Changing the type to '''attached''' has some consequences:
* IDs won't be contiguous as they used to be
* Storables won't be retrievable by old systems

==I/O and external operations==
===Before===
Any I/O operations could raise an exception upon failure.
===After===
No I/O operations will raise an exception upon failure.
===Rationale===
Writing exception free code for manipulating external resources is difficult at the moment, forcing you to use rescue clauses too many times in code that may have a very complex flow. Performing a check after the operation to see if it was successful is exception free but allows for a better and more accurate error reporting.
===Issues===
Changing the code would break too much code. The idea is to keep the existing as is, but add a new set of classes from a new I/O library outside of EiffelBase which will be exception free. It has mostly an impact on IO_MEDIUM descendants.

==Remove explicit creation procedure from <e>TUPLE</e>==
'''Scope:''' void-safety
====Before====
====After====
====Rationale====
Explicit creation of a <e>TUPLE</e> with attached reference fields introduces objects that break void-safety rules and make a system void-unsafe.
====Issues====
Some code needs to be redesigned to remove explicit <e>TUPLE</e> creation.
====Impact====
Low: explicit tuple creation can be flagged as obsolete by using regular Eiffel mechanism. After 1-2 releases the feature can be removed.

==Make <code>TUPLE</code> argument of features <code>{ROUTINE}.call</code> and <code>{FUNCTION}.item</code> attached==
'''Scope:''' void-safety
====Before====
<code>{ROUTINE}.call</code> and <code>{FUNCTION}.item</code> take argument of a type <code>detachable TUPLE</code>.
====After====
<code>{ROUTINE}.call</code> and <code>{FUNCTION}.item</code> take argument of a type <code>TUPLE</code>.
====Rationale====
It is possible that an agent object expects some arguments, but if it is passed <e>Void</e>, the compiler does not warn user about the issue.
====Issues====
All calls <e>.call (Void)</e> and <e>.item (Void)</e> need to be updated.
====Impact====
Very low: code can be updated by replacing <e>.call (Void)</e> with <e>.call</e>.

=Language Change=
==Reverse order of inheritance clauses==

==Dynamic dispatch==

==Non-conforming inheritance==

==Frozen/variant annotations==

Eiffel Breaking Changes

Eiffel Breaking Changes

2016-01-23T13:16:07Z

2016-01-21T12:17:20Z

Manus: Manus moved page Category:Language to Category:Eiffel Language without leaving a redirect

All documentation related to the Eiffel language