mirror of
https://github.com/EiffelSoftware/eiffel-org.git
synced 2026-02-12 05:25:17 +01:00
Author:admin
Date:2008-09-25T16:19:15.000000Z git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@44 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
jfiat
@@ -3,9 +3,9 @@
|
||||
[[Property:uuid|52206181-e002-0914-d98d-c817d32ec02e]]
|
||||
Located in the '''View''' menu, named either '''Link context tool''' or '''Unlink context tool''', this command allows you to switch between the two possible [[Address bars: Introduction|addressing modes]] . It is also accessible through the main toolbar ( [[Image:context-link-icon]] ).
|
||||
|
||||
{{note| '''Note''': This command only applies to the development window where it is invoked, and this setting is not automatically saved when exiting EiffelStudio. }}
|
||||
{{note|This command only applies to the development window where it is invoked, and this setting is not automatically saved when exiting EiffelStudio. }}
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Development Window Preferences|Change the default data sharing]] <br/>
|
||||
}}
|
||||
|
||||
|
||||
@@ -9,11 +9,11 @@ It also contains history arrows, and by clicking on the cluster, class or featur
|
||||
|
||||
[[Image:context-address-window]]
|
||||
|
||||
{{tip| '''Tip''': Labels in this address bar are pickable, to send the address to other tools easily. }}
|
||||
{{tip|Labels in this address bar are pickable, to send the address to other tools easily. }}
|
||||
|
||||
{{note| '''Note''': The context tool only has an address bar if it is unlinked from the editor. }}
|
||||
{{note|The context tool only has an address bar if it is unlinked from the editor. }}
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Change data share mode|Unlinking the context tool]] }}
|
||||
|
||||
|
||||
|
||||
@@ -12,9 +12,9 @@ It has several components:
|
||||
|
||||
It is possible to type a class or feature name to center the editor on it. Typing a class name that does not exist in the set of known classes pops up a dialog to create a class of that name.
|
||||
|
||||
{{tip| '''Tip''': Wildcards (* and ?) are available in these fields. }}
|
||||
{{tip|Wildcards (* and ?) are available in these fields. }}
|
||||
|
||||
{{tip| '''Tip''': The history is also accessible in the '''View/Go to''' menu. }}
|
||||
{{tip|The history is also accessible in the '''View/Go to''' menu. }}
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -11,9 +11,9 @@ Select the destination folder by expanding the tree and by clicking it. The top
|
||||
|
||||
Pressing '''OK''' moves the source item to the destination folder. Pressing '''Cancel''' discards the dialog box and does not move the source item.
|
||||
|
||||
{{tip| '''Tip''': You can also move items around by picking them in the favorites tree and dropping them where you want. }}
|
||||
{{tip|You can also move items around by picking them in the favorites tree and dropping them where you want. }}
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Favorites tree|Favorites tree]] <br/>
|
||||
}}
|
||||
|
||||
|
||||
@@ -9,7 +9,7 @@ Clicking on a class name sets its name in the top text field, whereas double-cli
|
||||
|
||||
The selected class goes to the root of the favorite tree. It is then possible to [[Move to Folder command|move]] it to a different favorite folder.
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Favorites tool: Introduction|Favorite tool]] <br/>
|
||||
[[Favorites menu|Favorite menu]] <br/>
|
||||
}}
|
||||
|
||||
@@ -10,7 +10,7 @@ A dialog is then popped up in which it is possible to select the name of the new
|
||||
Enabling the '''recursive''' option makes the compiler search not only the cluster directory but also all its sub-directories for classes. <br/>
|
||||
The '''library''' option optimizes compilations, since the classes inside a library cluster are compiled only once. However, if you modify the classes inside a library cluster, the modifications will not be taken into account in your project. Besides, you cannot add or remove classes in a library cluster, so use this option with care: if you intend to create new classes inside this cluster later in your design, do not select the library option. You should use this option only if the new cluster is given an existing directory, which already contains classes that you will not modify.
|
||||
|
||||
{{tip| '''Tip''': You don't have to enter a path for the new cluster if you choose to create a sub-cluster: the new cluster directory will be a sub-directory of the directory of the parent cluster, and its name will be the name of the newly created cluster. }}
|
||||
{{tip|You don't have to enter a path for the new cluster if you choose to create a sub-cluster: the new cluster directory will be a sub-directory of the directory of the parent cluster, and its name will be the name of the newly created cluster. }}
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -36,7 +36,7 @@ Search backwards: If this option is selected, the tool will highlight the previo
|
||||
'''Note''': If the search tool hits one end of the text, it will automatically continue from the other end. <br/>
|
||||
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
There are keyboard shortcuts and menu entries to launch searches without using the search tool directly. They are described the [[Search functionality|editor section]] of this help. }}
|
||||
|
||||
|
||||
|
||||
@@ -39,7 +39,7 @@ finish_freezing > c:\output_path\OUTPUT</code>
|
||||
|
||||
It will go the directory where your project is located and compile your Eiffel code using the `config.ecf' file located in your project directory and compile automatically the C code. All outputs will be stored in the file `c:\output_path/OUTPUT'.
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[EiffelStudio: Command line options|Command line compiler options]] }}
|
||||
|
||||
|
||||
|
||||
@@ -148,7 +148,7 @@ When running the Generate command with no arguments, you will be prompted for th
|
||||
You can also type in the arguments directly without waiting to be prompted, as in command => g profinfo finalize eiffel <br/>
|
||||
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Profiler Wizard|Profiler wizard]] }}
|
||||
|
||||
|
||||
|
||||
@@ -179,7 +179,7 @@ You must now run "finish_freezing" in:
|
||||
|
||||
with | replaced by \ if your platform is Windows, / if it is Unix. To execute the C compilation and linking part of the finalization, change directory to ''your_project_path''|EIFGENs|''target_name''|F_code as indicated and execute '''finish_freezing'''.
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Batch compilation|Batch compilation]] }}
|
||||
|
||||
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
[[Property:uuid|c22fad22-3dce-cf2c-1d24-4e70fc29f3f3]]
|
||||
==What's new==
|
||||
|
||||
{{seealso|See also: [[Differences between standard ECMA-367 and Eiffel Software implementation|Differences between standard ECMA-367 and Eiffel Software implementation]] }}
|
||||
{{seealso|[[Differences between standard ECMA-367 and Eiffel Software implementation|Differences between standard ECMA-367 and Eiffel Software implementation]] }}
|
||||
* Implemented once manifest strings. They can be used at the same places where normal manifest strings can be used, e.g.:
|
||||
<code>s := once "abc"
|
||||
io.put_string (once "Hello World!")</code>
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
[[Property:uuid|fc50f98f-4dfd-0173-23d4-9db219dde0cf]]
|
||||
==What's new==
|
||||
|
||||
{{seealso|See also: [[Differences between standard ECMA-367 and Eiffel Software implementation|Differences between standard ECMA-367 and Eiffel Software implementation]] }}
|
||||
{{seealso|[[Differences between standard ECMA-367 and Eiffel Software implementation|Differences between standard ECMA-367 and Eiffel Software implementation]] }}
|
||||
* Support for new expanded semantics defined in ECMA-367. The current limitations are: no copy semantics in the .NET code generation, and still no generic conformance.
|
||||
* Inline agents as defined in ECMA-367 with the limitation to only accept the do form.
|
||||
* Added possibility to define agents on attributes or externals.
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
[[Property:uuid|83f6c19c-b0da-6acb-0333-a92d445cfe56]]
|
||||
==What's new==
|
||||
|
||||
{{seealso|See also: [[Differences between standard ECMA-367 and Eiffel Software implementation|Differences between standard ECMA-367 and Eiffel Software implementation]] }}
|
||||
{{seealso|[[Differences between standard ECMA-367 and Eiffel Software implementation|Differences between standard ECMA-367 and Eiffel Software implementation]] }}
|
||||
* Added support for multiple constraints in formal generic parameters.
|
||||
* The root class can now be a generic class, and thus one can now specify a root type.
|
||||
* The notion of creation readiness according to ECMA Eiffel standard (2nd edition, chapter 8.12.12) is implemented.
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
[[Property:uuid|32beeca8-08df-4918-b231-8a14114fdd62]]
|
||||
==What's new==
|
||||
|
||||
{{seealso|See also: [[Differences between standard ECMA-367 and Eiffel Software implementation|Differences between standard ECMA-367 and Eiffel Software implementation]] }}
|
||||
{{seealso|[[Differences between standard ECMA-367 and Eiffel Software implementation|Differences between standard ECMA-367 and Eiffel Software implementation]] }}
|
||||
* Multiple errors are reported for each compilation degree.
|
||||
* Experimental support for Non-conforming Inheritance has been added (Classic only). Classes may now be inherited (using inherit {NONE} but no conformance of that class is implied.
|
||||
* Attachment marks are supported. Now it's possible to specify whether an entity is attached or detachable:
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
[[Property:uuid|20122f4c-22c6-d0ee-c38b-36908ca86ad2]]
|
||||
==What's new==
|
||||
|
||||
{{seealso|See also: [[Differences between standard ECMA-367 and Eiffel Software implementation|Differences between standard ECMA-367 and Eiffel Software implementation]] }}
|
||||
{{seealso|[[Differences between standard ECMA-367 and Eiffel Software implementation|Differences between standard ECMA-367 and Eiffel Software implementation]] }}
|
||||
* Exceptions as objects are now implemented.
|
||||
* Added support for new ~ operator which can compare 2 objects safely regardless of their type.
|
||||
* Added detection of harmful catcall at runtime (harmless ones are currently ignored).
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
[[Property:link_title|]]
|
||||
[[Property:weight|-9]]
|
||||
[[Property:uuid|fc1e73f4-5646-aa41-e7fe-97dc6f3ceb04]]
|
||||
{{seealso|See also: [[Differences between standard ECMA-367 and Eiffel Software implementation|Differences between standard ECMA-367 and Eiffel Software implementation]] }}
|
||||
{{seealso|[[Differences between standard ECMA-367 and Eiffel Software implementation|Differences between standard ECMA-367 and Eiffel Software implementation]] }}
|
||||
|
||||
==Added classes==
|
||||
* New basic classes have been added: <eiffel>INTEGER_8</eiffel>, <eiffel>INTEGER_16</eiffel>, <eiffel>INTEGER_64</eiffel> and <eiffel>WIDE_CHARACTER</eiffel>. <eiffel>INTEGER</eiffel> is now specified as having a 32 bits representation
|
||||
|
||||
@@ -9,7 +9,7 @@ The dynamic library window that appears when selecting this menu is mainly compo
|
||||
|
||||
[[Image:shared-library-window]]
|
||||
|
||||
{{note| '''Note''': The layout of this wizard is slightly different on Windows and on Unix systems, because the index and calling convention fields never appear on Unix systems. }}
|
||||
{{note|The layout of this wizard is slightly different on Windows and on Unix systems, because the index and calling convention fields never appear on Unix systems. }}
|
||||
|
||||
To add a new feature to the definition file, you can either:
|
||||
* Pick the feature from any place in EiffelStudio and drop it into the list. If several creation procedures exists in the container class, a dialog is popped up to give the choice between all possible creation procedures.
|
||||
@@ -23,7 +23,7 @@ It is also possible to check the validity of the definition file. This command
|
||||
|
||||
Other commands, located in the '''File''' menu, give standard file operations, such as opening [[Image:general-open-icon]] a definition file, creating a new definition file [[Image:new-document-icon]] ,or saving the current definition file [[Image:16x16--general-save-icon]] .
|
||||
|
||||
{{tip| '''Tip''': Although the wizard can handle several files during the same EiffelStudio session, remember that only one file can be used in the project settings to effectively generate a shared library. }}
|
||||
{{tip|Although the wizard can handle several files during the same EiffelStudio session, remember that only one file can be used in the project settings to effectively generate a shared library. }}
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@
|
||||
[[Property:uuid|f3926dd7-eb68-7a82-39f0-b4f5ea891436]]
|
||||
Basically, once the Eiffel definition file is created, the compiler will generate a set of files and will compile them to generate the Dynamic library into the ''EIFGENs/target_name/W_code'' or ''EIFGENs/target_name/F_code'' directory.
|
||||
|
||||
{{note| '''Note''': To generate and compile these files, you have to indicate the definition file that should be used in the [[Advanced Options|advanced node of the project settings]] of your system. This way EiffelStudio will know which one to use. If you do not specify any definition file, nothing will be generated. }}
|
||||
{{note|To generate and compile these files, you have to indicate the definition file that should be used in the [[Advanced Options|advanced node of the project settings]] of your system. This way EiffelStudio will know which one to use. If you do not specify any definition file, nothing will be generated. }}
|
||||
|
||||
The set of files is composed of:
|
||||
<div>
|
||||
|
||||
@@ -62,7 +62,7 @@ Auto-complete feature name: [[Image:console-auto3|Auto-complete feature name]]
|
||||
|
||||
You can also pick and drop a group/class/feature into the command area to have related name/path inserted.
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[External commands editor dialog|External commands Editor dialog]] }}
|
||||
|
||||
|
||||
|
||||
@@ -53,7 +53,7 @@ Note that any existing breakpoint can be referenced by an implicit tag with ''"'
|
||||
|
||||
<center> [[Image:breakpoint-dialog-when-hits]] </center>
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Breakpoint commands|Breakpoint commands]] <br/>
|
||||
[[Breakpoint information command|Breakpoint information command]] <br/>
|
||||
}}
|
||||
|
||||
@@ -17,7 +17,7 @@ Note: you can sort by clicking the column, especially the first column which pro
|
||||
<center>Display all breakpoints in a list filtered by a tag using button [[Image:breakpoints-list-filter-button]] <br/>
|
||||
[[Image:breakpoints-list-filter]] </center>
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Breakpoint commands|Breakpoints commands]] <br/>
|
||||
[[Breakpoint information command|Breakpoint information command]] <br/>
|
||||
}}
|
||||
|
||||
@@ -14,7 +14,7 @@ The condition is a Boolean expression that follows the same rule as the expressi
|
||||
|
||||
{{warning|'''Caution''': if you enter an expression that is not supported or which raises an error during evaluation, by default the condition is considered as True (then the debugger will stop) }}
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Breakpoint editing|Breakpoint menu]] <br/>
|
||||
[[Breakpoint commands|Breakpoints commands]] <br/>
|
||||
[[Breakpoint information command|Breakpoint information command]] <br/>
|
||||
|
||||
@@ -7,7 +7,7 @@ If an application was stopped, it attempts to execute the instruction located on
|
||||
|
||||
It is accessible through the '''project''' toolbar ( [[Image:debug-step-over-icon]] ) or through the '''debug''' menu.
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Eiffel Debugger Execution: Introduction|Execution commands]] <br/>
|
||||
[[Generating executables|Compiling in Workbench mode]] }}
|
||||
|
||||
|
||||
@@ -7,7 +7,7 @@ This gives access to dynamic information concerning the application, such as the
|
||||
|
||||
It is accessible through the '''project''' toolbar ( [[Image:debug-pause-icon]] ) or through the '''debug''' menu.
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Eiffel Debugger Execution: Introduction|Execution commands]] }}
|
||||
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ This command launches an application compiled in Work Bench mode. The applicatio
|
||||
|
||||
It is accessible through the '''project''' toolbar ( [[Image:debug-run-icon]] ) or through the '''debug''' menu.
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Eiffel Debugger Execution: Introduction|Execution commands]] <br/>
|
||||
[[Generating executables|Compiling in Workbench mode]] }}
|
||||
|
||||
|
||||
@@ -7,7 +7,7 @@ No debugging is possible with this command, but it lets you test the real speed
|
||||
|
||||
It is accessible through the '''project''' toolbar ( [[Image:debug-run-finalized-icon]] ) or through the '''project''' menu.
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Eiffel Debugger Execution: Introduction|Execution commands]] <br/>
|
||||
[[Generating executables|Compiling in finalized mode]] }}
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ This command launches an application compiled in Workbench mode. The application
|
||||
|
||||
It is accessible through the '''project''' toolbar ( [[Image:debug-run-without-breakpoint-icon]] ) or through the '''debug''' menu.
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Eiffel Debugger Execution: Introduction|Execution commands]] <br/>
|
||||
[[Generating executables|Compiling in Workbench mode]] }}
|
||||
|
||||
|
||||
@@ -7,7 +7,7 @@ If an application was stopped, it attempts to enter the feature located on the e
|
||||
|
||||
It is accessible through the '''project''' toolbar ( [[Image:debug-step-into-icon]] ) or through the '''debug''' menu.
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Eiffel Debugger Execution: Introduction|Execution commands]] <br/>
|
||||
[[Generating executables|Compiling in Workbench mode]] }}
|
||||
|
||||
|
||||
@@ -7,7 +7,7 @@ If an application was stopped, it attempts to exit the feature where the applica
|
||||
|
||||
It is accessible through the '''project''' toolbar ( [[Image:debug-step-out-icon]] ) or through the '''debug''' menu.
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Eiffel Debugger Execution: Introduction|Execution commands]] <br/>
|
||||
[[Generating executables|Compiling in Workbench mode]] }}
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ This command kills the debugged application, if any. This stops the debugging se
|
||||
|
||||
It is accessible through the '''project''' toolbar ( [[Image:debug-stop-icon]] ) or through the '''debug''' menu.
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Eiffel Debugger Execution: Introduction|Execution commands]] }}
|
||||
|
||||
|
||||
|
||||
@@ -11,9 +11,9 @@ In the screenshot, you can see various expressions, the 4th one, is a dropped ob
|
||||
|
||||
The 5th expression has an error, the icon is different, and the 'value' shows there is an error, double click on it for more details
|
||||
|
||||
{{tip| '''Tip''': If the expression returns a non-Void (and non basic type) object, then the corresponding row in the list is pickable, and can be dropped for example in the Watch tool to evaluate expression on it, or even to keep the object over the steppings. }}
|
||||
{{tip|If the expression returns a non-Void (and non basic type) object, then the corresponding row in the list is pickable, and can be dropped for example in the Watch tool to evaluate expression on it, or even to keep the object over the steppings. }}
|
||||
|
||||
{{tip| '''Tip''': holding the mouse pointer over the expression's cell will popup a tooltip with details on the pointed expression }}
|
||||
{{tip|holding the mouse pointer over the expression's cell will popup a tooltip with details on the pointed expression }}
|
||||
|
||||
On top of the list, four buttons can be found.
|
||||
* the button [[Image:toolbar-dropdown-icon]] is used to create/close watch tools via a menu popup
|
||||
@@ -35,7 +35,7 @@ The associated key shortcut is F2.
|
||||
The associated key shortcut is Del.
|
||||
* And the last two buttons are used to move up and down the expressions. You can also move the expressions up and down using [CONTROL] + [-] or [CONTROL] + [+].
|
||||
|
||||
{{tip| '''Tip''': Dropping an object onto this list lets you define quickly an expression whose context is the dropped object. This avoids having to type object addresses manually. <br/>
|
||||
{{tip|Dropping an object onto this list lets you define quickly an expression whose context is the dropped object. This avoids having to type object addresses manually. <br/>
|
||||
If you press the [Control] key during the dropping, you will add the dropped object as itself. }}
|
||||
|
||||
|
||||
|
||||
@@ -5,9 +5,9 @@ In both grids of the [[Objects tool: Introduction|object tool]] , objects are di
|
||||
|
||||
To do so, inherit from the class <eiffel>DEBUG_OUTPUT</eiffel> in the classes that should let their objects display a string value, and implement the `debug_output' feature. At run-time, the debugger will automatically query the result of this feature on all objects that define it and display it in the object tool and the [[Expression evaluation|evaluation tool]] .
|
||||
|
||||
{{sample| '''Sample''': The <eiffel>NUMERIC</eiffel> class inherits from the <eiffel>DEBUG_OUTPUT</eiffel> one so that it is possible to see the value of *_REF objects without expanding them. }}
|
||||
{{sample|The <eiffel>NUMERIC</eiffel> class inherits from the <eiffel>DEBUG_OUTPUT</eiffel> one so that it is possible to see the value of *_REF objects without expanding them. }}
|
||||
|
||||
{{tip| '''Tip''': If an object has a long string output or an output with carriage returns, for instance, pick-and-drop it to the expanded display command [[Image:debugger-expand-info-icon]] in the object tool. }}
|
||||
{{tip|If an object has a long string output or an output with carriage returns, for instance, pick-and-drop it to the expanded display command [[Image:debugger-expand-info-icon]] in the object tool. }}
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -11,7 +11,7 @@ Depending the nature of the dropped object, you can view it with several viewers
|
||||
* '''Object browse''': browse the object, as you would do in objects or watch tools
|
||||
* '''Object internal''': display a few internal data such as <code>class_name</code>, <code>type_name</code>, <code>dynamic_type</code>, <code>field_count</code>, <code>deep_physicial_size</code>, and <code>physical_size</code>
|
||||
|
||||
{{note|Note that the "string display" viewer is available for object with a string representation, for instance object conformed to [[ref:/libraries/base/reference/string_8_chart]] or conform to [[ref:/libraries/base/reference/debug_output_chart]] (see [[Debug output|Debug Output]] )}}
|
||||
{{note|that the "string display" viewer is available for object with a string representation, for instance object conformed to [[ref:/libraries/base/reference/string_8_chart]] or conform to [[ref:/libraries/base/reference/debug_output_chart]] (see [[Debug output|Debug Output]] )}}
|
||||
|
||||
{{note|And the "XML display" is available for object eligible to "String display", and whose string representation has XML content. The viewer is display XML in a basic tree enabled grid.}}
|
||||
|
||||
|
||||
@@ -7,7 +7,7 @@ Accessible via the '''Debug/Overflow prevention...''' menu, this command makes i
|
||||
|
||||
By default a warning is issued when the debugged program reaches a stack depth of 1,000 elements.
|
||||
|
||||
{{note| '''Note''': Once an application has stopped at the selected level, it will not stop again until its stack depth goes below the critical stack depth again. }}
|
||||
{{note|Once an application has stopped at the selected level, it will not stop again until its stack depth goes below the critical stack depth again. }}
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -25,7 +25,7 @@ The diagram tool uses the [http://bon-method.com BON] (Business Object Notation
|
||||
[[Image:bon-class-root]]
|
||||
|
||||
|
||||
{{seealso| '''See also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Rename class|Changing class names]] }}
|
||||
|
||||
==Cluster==
|
||||
@@ -33,7 +33,7 @@ The diagram tool uses the [http://bon-method.com BON] (Business Object Notation
|
||||
A cluster is a collection of classes and sub-clusters. It is represented by a stippled, rounded rectangle. The cluster name is in a similar rectangle, by default located at the top of the cluster just outside of it. A cluster can be iconified, which means it is minimized to take up as less space as possible.
|
||||
<div> [[Image:bon-cluster-iconified]] [[Image:bon-cluster]] </div><br/>
|
||||
|
||||
{{seealso| '''See also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Iconifying and restoring a cluster|Iconifying a cluster]] }}
|
||||
|
||||
==Inheritance links==
|
||||
@@ -42,7 +42,7 @@ Inheritance between classes is represented by an arrow from a class to its paren
|
||||
<div> [[Image:bon-inheritance]] </div><br/>
|
||||
<br/>
|
||||
|
||||
{{seealso| '''See also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Creating inheritance links|Creating inheritance links]] }}
|
||||
|
||||
==Client/supplier links==
|
||||
@@ -51,7 +51,7 @@ Client relationships between classes are represented by an arrow with a double l
|
||||
<div> [[Image:bon-client]] [[Image:bon-agg-client]] </div><br/>
|
||||
<br/>
|
||||
|
||||
{{seealso| '''See also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Creating client/supplier links|Creating client/supplier links]] }}
|
||||
|
||||
|
||||
|
||||
@@ -11,9 +11,9 @@
|
||||
* <''classe''>, in the form of class=to_be_replaced, '''to_be_replaced''' is the name of the class.
|
||||
* <''featuree''>, in the form of feature=to_be_replaced, '''to_be_replaced''' is the name of the feature.
|
||||
|
||||
{{note| '''Note: '''All parts above are unordered. }}
|
||||
{{note|All parts above are unordered. }}
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[EIS incoming Examples|Examples]] }}
|
||||
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@
|
||||
Annotations may be applicable to:
|
||||
* An individual class or feature. In this case the annotation figures in the class text, as part of an Eiffel "note" clause ("indexing" is still supported, it depends on which syntax level users choose).
|
||||
* A target, library or cluster. In this case the annotation figures in the associated ECF file; EiffelStudio provides support for entering it through a Information (EIS) Tool.
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Information Tool|Information Tool]] }}
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@ The following example illustrates the basic form of an EIS note entry:
|
||||
|
||||
The label (Node_entry as called in the ECMA/ISO Eiffel Standard syntax) is '''EIS'''. '''EIS''' Note_value tells the Eiffel Information System that this Note_entry is of interest to EIS, as distinct from any other information that might be expressed through a Note_entry. The file name (src) includes '''$PROJ''', referring to a variable, defining the project location. The protocol is PDF. The '''nameddest''' property (name destination) is a specific property of PDF documents. The tag '''requirement''' indicating that this entry links the enclosing Eiffel class or feature with some parts of the requirement documents.
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Variable Definition|Variable Definition]] }}
|
||||
<code><note ise_support="EIS" protocol="pdf" name="Project Requirement" src="($PROJ)/docs/requirements.pdf" nameddest="4.1"/></code>
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
[[Property:weight|1]]
|
||||
[[Property:uuid|696457ef-ac1f-40c1-a0da-54900d9cccf8]]
|
||||
Information Tool provides information management functions: adding, modifying and removing.
|
||||
{{note| '''Note: '''Annotation management is only available in lists coresponding to nodes rather than tag nodes - all tags and "Items without tag". }}
|
||||
{{note|Annotation management is only available in lists coresponding to nodes rather than tag nodes - all tags and "Items without tag". }}
|
||||
|
||||
==Adding==
|
||||
|
||||
@@ -13,7 +13,7 @@ For each kind of nodes in the information tree, related annotations are listed i
|
||||
To modify an annotation, one can use Information Tool or do it by code.
|
||||
* By Information Tool, a line in the annotation list should be selected, then click into columns and activate editing/choosing mode. Once the editing area/drop down list is deactivated, the modification is done and synchronized into code automatically.
|
||||
* By code, one simply modifies code in the editor, or .ecf files in external editor (not recommented).
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[EIS: Outgoing|Syntax for Annotations]] }}
|
||||
|
||||
|
||||
@@ -21,7 +21,7 @@ To modify an annotation, one can use Information Tool or do it by code.
|
||||
|
||||
By pressing '''Delete''', or clicking the third button on the bottom toolbar deletes all selected annotations in the list. And corresponding code is synchronized.
|
||||
|
||||
{{note| '''Note: '''Annotation list can be multi-selected. }}
|
||||
{{note|Annotation list can be multi-selected. }}
|
||||
|
||||
{{note| All means to manage annotations via the tool are inreversible, except that the location - class or feature - has been opened in the editor, thus undo can be achieved via the editor. Removing is prompted on user demands. The tag tree is automatically updated when annotations are added/modified/removed or through system sweeping. }}
|
||||
|
||||
|
||||
@@ -12,7 +12,7 @@ EIS supports following types of variables which can be used in '''Source''' of a
|
||||
** group_name
|
||||
** target_name
|
||||
|
||||
{{note|'''Note: '''This kind of variables can only be used in components that are enclosed in those the variable name refers to. For example, '''feature_name''' has no effect if used in a target component.}}
|
||||
{{note|This kind of variables can only be used in components that are enclosed in those the variable name refers to. For example, '''feature_name''' has no effect if used in a target component.}}
|
||||
|
||||
* Individual system or library preferences. This kind of variables are defined in .ecf files, can be accessed via Project Setting dialog.
|
||||
{{note|System -> Target -> Advanced -> Variables}}
|
||||
|
||||
@@ -11,13 +11,13 @@ To complete your code with the selected item, press "Enter" or "Ctrl+Space". <br
|
||||
To choose another item, use keyboard Up and Down arrows or the mouse. You can also modify the content of the text field. The list will be updated automatically. To validate your choice, press "Enter" or "Ctrl+Space". If there is no selected item, the content of the text field will be inserted. <br/>
|
||||
To cancel the auto-complete, press "Esc" at any time.
|
||||
|
||||
{{tip| '''Tips''': }}
|
||||
{{tip|s''': }}
|
||||
* If the selected feature is a query, you can call the auto-complete again right after the previous completion. There is no need to type a dot.
|
||||
* You can call the auto-complete without an identifier. The auto-complete window will then show the features of the current class.
|
||||
* The keyboard shortcut for automatic completion can be changed in the [[Keyboard shortcuts preferences|editor preferences]] .
|
||||
* Typing a non-alphanumeric character in the completion window automatically closes it. You can therefore type '.', ' ' or '(' to close the completion window and start typing the next token straight away.
|
||||
|
||||
{{note| '''Notes''': }}
|
||||
{{note|s''': }}
|
||||
* Only identifiers that were already defined when the class was compiled for the last time can be completed, except for local entity names that can always be completed.
|
||||
* Only compiled features will appear in the auto-complete window.
|
||||
* By default, features from class ANY will be ignored by the auto-complete window. This can be changed in the [[General Editor Preferences|editor preferences]] .
|
||||
|
||||
@@ -61,7 +61,7 @@ The editor can complete syntactic structures or part of them. The auto-complete
|
||||
The way these reserved words are completed is fully [[Syntax automatic completion preferences|customizable]] .
|
||||
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
To see how the editor completes by default and how it can be changed, please read the following pages: [[Syntax automatic completion preferences|Syntax auto-complete preferences]] <br/>
|
||||
}}
|
||||
|
||||
|
||||
@@ -8,7 +8,7 @@ If you choose to use the mouse, just click in the text where you want the cursor
|
||||
The keys that you may use to move the cursor in EiffelStudio editor are "Home", "End", "Page up", "Page Down" and the four arrows. Pressing "Home" will make the cursor go to the beginning of the line. Pressing "End" will move the cursor to the end of the line. You can use "Page Up" to move the cursor one page closer to the beginning of the text. Pressing "Page down" will position the cursor one page further. <br/>
|
||||
Left and Right arrows can be used to move respectively to the character on the left or on the right of current position. Up and Down arrows allow you to move the cursor to the previous and next lines.
|
||||
|
||||
{{tip| '''Tip''': By maintaining "Ctrl" pressed as you use Left and Right arrows, you will move the cursor to the next or previous word instead of the next or previous character. }}
|
||||
{{tip|By maintaining "Ctrl" pressed as you use Left and Right arrows, you will move the cursor to the next or previous word instead of the next or previous character. }}
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -10,7 +10,7 @@ The "Uncomment" command corresponds to the '''Uncomment''' entry in the '''Advan
|
||||
|
||||
|
||||
|
||||
{{note| '''Note''': If there is no selection, these commands will be applied to the current line. }}
|
||||
{{note|If there is no selection, these commands will be applied to the current line. }}
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -7,7 +7,7 @@ EiffelStudio editor offers the possibility to embed several lines in "if then...
|
||||
* The first command corresponds to the '''Embed in if''' entry in the '''Advanced''' submenu of the [[Edit menu commands]] [[Edit menu commands| Menu]] . It may be called by using the keyboard shortcut "Ctrl+I" too. Its action is to insert a line with "if then" before the [[Selection|selected]] lines and a line with "end" after those lines. The lines will be indented and the cursor positioned between "if" and "then".
|
||||
* The second command corresponds to the '''Embed in debug''' entry in the '''Advanced''' submenu of the [[Edit menu commands]] [[Edit menu commands| Menu]] . It may be called by using the keyboard shortcut "Ctrl+D" too. Its action is to insert a line with "debug" before the [[Selection|selected]] lines and a line with "end" after those lines. The lines will be indented and the cursor positioned after "debug" and "then".
|
||||
|
||||
{{note| '''Note''': If there is no selection, these commands will be applied to the current line. }}
|
||||
{{note|If there is no selection, these commands will be applied to the current line. }}
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -11,7 +11,7 @@ The "Unindent" command corresponds to the '''Unindent selection''' entry in the
|
||||
|
||||
|
||||
|
||||
{{note| '''Note''': If there is no selection, you may still use the unindent shortcut "Shift+Tab". The command will be applied to the current line. <br/>
|
||||
{{note|If there is no selection, you may still use the unindent shortcut "Shift+Tab". The command will be applied to the current line. <br/>
|
||||
}}
|
||||
|
||||
|
||||
|
||||
@@ -19,7 +19,7 @@ Search the previous occurrence of the current selected pattern. <br/>
|
||||
To do so, press "Ctrl+Shift+F3". You can change this key binding in [[Keyboard shortcuts preferences|the preferences]] .
|
||||
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Search tool|Search tool]] }}
|
||||
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ In EiffelStudio editor, you can select text by using either the mouse or the key
|
||||
|
||||
To select a text zone with the keyboard, [[Cursor moves|move the cursor]] to one end of the zone. Then press "Shift" and maintain the key pressed until you moved the cursor to the other end of the zone. The selected zone will appear in reverse video. If you want to select the entire text, press "Ctrl" and "A".
|
||||
|
||||
{{tip| '''Tip''': You can combine "Ctrl" and "Shift" when using Left and Right arrows to select text word by word }}
|
||||
{{tip|You can combine "Ctrl" and "Shift" when using Left and Right arrows to select text word by word }}
|
||||
|
||||
If you choose to use the mouse, first [[Cursor moves|position the cursor]] to one end of the text zone you want to select, and click there without releasing the mouse button. Then move the mouse pointer to the other end of the zone and release the button. The selected text is shown in reverse video. If the other end of the zone is not visible, move the mouse pointer out of the edition area as you select text in the direction where the end is. EiffelStudio Editor will start scrolling automatically and will stop as soon as the mouse pointer enters the edition area again.
|
||||
|
||||
|
||||
@@ -13,7 +13,7 @@ Right-clicking when the pebble is crossed will only stop the pick-and-drop becau
|
||||
|
||||
* If, for any reason, you change your mind, you can cancel the pick-and-drop by left-clicking anywhere or by pressing the Escape key.
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Pick-and-drop shortcut|Pick-and-drop shortcut]] <br/>
|
||||
}}
|
||||
|
||||
|
||||
@@ -3,9 +3,9 @@
|
||||
[[Property:uuid|2cb70fcf-913c-0b74-d2a9-5928caa5904a]]
|
||||
In the [[EiffelStudio Editor Introduction|editor]] and the [[EiffelStudio window overview|context tool]] , pressing the '''control''' key while right-clicking on a development object opens a new development window which is centered on the clicked object.
|
||||
|
||||
{{tip| '''Tip''': The effect of control-picking is now configurable in the [[Preferences Reference|preferences]] . }}
|
||||
{{tip|The effect of control-picking is now configurable in the [[Preferences Reference|preferences]] . }}
|
||||
|
||||
{{seealso| '''See Also'''<br/>
|
||||
{{seealso|<br/>
|
||||
[[Pick-and-drop mechanism|Pick-and-drop mechanism]] }}
|
||||
|
||||
|
||||
|
||||
@@ -14,13 +14,13 @@ To remove an icon, click on it in the right list and click on '''<- Remove'''.
|
||||
|
||||
The order of the icons in the right list is the same as in the toolbar. If you want to move an icon in the list, select it and use '''Up''' and '''Down''' buttons. '''Up''' will move it to the top, i.e. to the left of the toolbar. '''Down''' will move it in the opposite direction.
|
||||
|
||||
{{tip| '''Tip''': You can also pick-and-drop icons to organize them. }}
|
||||
{{tip|You can also pick-and-drop icons to organize them. }}
|
||||
|
||||
Lastly, some icons can be displayed with an explanatory text. A menu at the bottom of the window will allow you to choose if the text should be displayed. The tables below present the list of these icons for both toolbars and what they look like with and without text.
|
||||
|
||||
Once you made the changes you wanted, validate them by clicking on '''OK'''. You can also go back to the initial toolbar layout by clicking on '''C ancel'''.
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Main toolbars|Toolbars Reference]] }}
|
||||
|
||||
|
||||
|
||||
@@ -128,7 +128,7 @@ This shortcut may be customized.
|
||||
|}
|
||||
|
||||
|
||||
{{note| '''Note''': These shortcuts are not available everywhere. All operations that do not imply changes in the text are available both in the editor and in the class and feature tabs of the context tool. Other operations are available only in the editor. }}
|
||||
{{note|These shortcuts are not available everywhere. All operations that do not imply changes in the text are available both in the editor and in the class and feature tabs of the context tool. Other operations are available only in the editor. }}
|
||||
|
||||
==Compiler==
|
||||
|
||||
|
||||
@@ -60,7 +60,7 @@ The context tool, located in the right panel, is a major part of EiffelStudio. I
|
||||
|
||||
By default, the context tool is unlinked from the rest of the window, which means all left tools refer to the object that is in the editor and the main toolbar, while the context tool (and the debug tools if they are present) displays information concerning a different object. It is possible to link the context tool, so that the whole development window displays information relative to the same development object.
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[EiffelStudio: A Guided Tour|EiffelStudio Guided Tour]] <br/>
|
||||
[[Browsing tools: Introduction|Browsing tools]] <br/>
|
||||
[[Main toolbars|Toolbar customization]] <br/>
|
||||
|
||||
@@ -9,7 +9,7 @@ You can hide toolbars (or the address bar) by unselecting them in the '''Toolbar
|
||||
In the standard toolbar, you will find buttons to manage [[Browsing tools: Introduction|tools]] and windows or that are related to the [[EiffelStudio Editor Introduction|editor]] . <br/>
|
||||
|
||||
|
||||
{{note| '''Note''': For both toolbars, it is possible to choose which buttons are displayed and which ones are not. See the [[Toolbar customization|Toolbars customization page]] for more information. }}
|
||||
{{note|For both toolbars, it is possible to choose which buttons are displayed and which ones are not. See the [[Toolbar customization|Toolbars customization page]] for more information. }}
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -13,10 +13,10 @@ There are several kinds of preferences:
|
||||
* Shortcut preferences : edit the value cell, and press the wanted shortcuts..
|
||||
* Other preferences : They will be modified by typing their value directly into an editable text field.
|
||||
If there is no message stating you need to restart EiffelStudio, changes will be taken into account immediately.
|
||||
{{tip| '''Tip''': below the table, you will find a text field with the internal name of the preference (for instance: ''editor.eiffel.auto-complete_...''). }}
|
||||
{{tip|below the table, you will find a text field with the internal name of the preference (for instance: ''editor.eiffel.auto-complete_...''). }}
|
||||
|
||||
|
||||
{{tip| '''Tip''': you can export preferences to xml file, and import from xml file, this can be convenient when reinstalling EiffelStudio). }}
|
||||
{{tip|you can export preferences to xml file, and import from xml file, this can be convenient when reinstalling EiffelStudio). }}
|
||||
|
||||
|
||||
{{warning| '''Caution''': You can restore preferences default values by clicking on the "Restore Default" button. ALL preferences will be reset. }}
|
||||
|
||||
@@ -500,7 +500,7 @@ Default value for [[Keywords automatic completion preferences|"Customized autoco
|
||||
<br/>
|
||||
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Keywords automatic completion preferences|Keywords automatic completion preferences]] <br/>
|
||||
[[Keyword completion customization|Keyword completion customization]] <br/>
|
||||
}}
|
||||
|
||||
@@ -66,10 +66,10 @@ The four ''%B'' will remove ''end'' plus one character before ''end'' (the tabul
|
||||
''$indent$%B$cursor$'' means that the cursor will be moved to the end of the line where one less blank space than before the original ''end'' will have been inserted.
|
||||
|
||||
|
||||
{{note| '''Note''': EiffelStudio editor can insert spaces instead of tabulation when you use special character ''%T''. This is set in [[General Editor Preferences|another section of the preferences]] . <br/>
|
||||
{{note|EiffelStudio editor can insert spaces instead of tabulation when you use special character ''%T''. This is set in [[General Editor Preferences|another section of the preferences]] . <br/>
|
||||
}}
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Keywords automatic completion preferences|Keywords automatic completion preferences]] <br/>
|
||||
[[Default values for keyword completion preferences|Default values for keyword completion preferences]] <br/>
|
||||
}}
|
||||
|
||||
@@ -102,7 +102,7 @@ Feature views indices:
|
||||
|}
|
||||
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[EiffelStudio Tools Preferences|Preferences for other tools]] }}
|
||||
|
||||
|
||||
|
||||
@@ -167,7 +167,7 @@ This category gathers the preferences related to the EiffelStudio BON Diagram to
|
||||
| Color for UML inheritance links.
|
||||
|}
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[EiffelStudio Tools Preferences|Preferences for other tools]] }}
|
||||
|
||||
|
||||
|
||||
@@ -9,7 +9,7 @@
|
||||
* Dead Code Removal: should unused code be removed? (C code generation mode only)
|
||||
* Dynamic Runtime: makes the generated executable use a shared library version of the runtime on both Windows (DLL) and Unix platforms (.so) that supports shared libraries.(C code generation mode only)
|
||||
|
||||
{{note| '''Note''': On Windows, the dynamic run-time is available only if you compile with the Microsoft Visual compiler. }}
|
||||
{{note|On Windows, the dynamic run-time is available only if you compile with the Microsoft Visual compiler. }}
|
||||
* Enforce unique class names: enforce all class names to be system wide unique?
|
||||
* Exception Trace: makes it possible to see a complete exception trace in a finalized application. Because it is adding some code to remember where the application was during the crash it can slow down the performance of your application by a factor of 5% to 30% depending of your platform. (C code generation mode only)
|
||||
* Inlining, Inlining Size: enables inlining on Eiffel features that can be inlined, i.e. whose size is less or equal to the specified size in the combo box. The size value given in parameter corresponds to the number of instructions as seen by the Eiffel compiler (for example a := b.f corresponds to 2 instructions). The inlining is very powerful since it can inline a function in all your Eiffel code, without scope limitation as found in C or C++ compilers. (C code generation mode only)
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
The ancestors view [[Image:class-ancestors-icon]] displays all the classes from which the current class inherits, directly or not, using a tree-like indented layout. <br/>
|
||||
It is available through the '''Class''' tab of the [[EiffelStudio window overview|context tool]] .
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Descendants|Descendants]] }}
|
||||
|
||||
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
The attributes view [[Image:class-features-attribute-icon]] displays all the attributes of the current class, including inherited attributes. <br/>
|
||||
It is available through the '''Class''' tab of the [[EiffelStudio window overview|context tool]] .
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Routines|Routines]] }}
|
||||
|
||||
|
||||
|
||||
@@ -9,7 +9,7 @@ In this view, most of the development objects are [[Pick-and-drop mechanism|clic
|
||||
|
||||
'''Note''': The generated text is not editable, but it is compilable. This view is not available to .NET classes which are imported through by means of an assembly. This is because the assembly .exe or .dll exposes only the interface methods and therefore is no implementation to display. Such classes may be viewed, in a clickable format using the Contract View or Interface View.
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[EiffelStudio Editor|Editor]] }}
|
||||
|
||||
|
||||
|
||||
@@ -5,9 +5,9 @@ The flat view [[Image:view-flat-icon]] displays all the features for the curren
|
||||
|
||||
{{warning| '''Caution''': For classes with many [[Ancestors|ancestors]] , computation of the flat view may require a few seconds. }}
|
||||
|
||||
{{note| '''Note''': This view is not available to .NET classes which are imported through by means of an assembly. This is because the assembly .exe or .dll exposes only the interface methods and therefore is no implementation to display. Such classes may be viewed, in a clickable format using the Contract View or Interface View. }}
|
||||
{{note|This view is not available to .NET classes which are imported through by means of an assembly. This is because the assembly .exe or .dll exposes only the interface methods and therefore is no implementation to display. Such classes may be viewed, in a clickable format using the Contract View or Interface View. }}
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Flat Contract view|Flat Contract view]] }}
|
||||
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@
|
||||
[[Property:uuid|8ddd0d2a-d4db-b0b6-8ee1-63e205a53dcc]]
|
||||
The clickable view [[Image:view-clickable-icon]] allows to [[Pick-and-drop mechanism|pick]] every class or feature name in the class text and is available either through the [[EiffelStudio Editor|editor]] or through the '''Class''' tab of the [[EiffelStudio window overview|context tool]] .
|
||||
|
||||
{{note| '''Note''': This view is not available to .NET classes which are imported through by means of an assembly. This is because the assembly .exe or .dll exposes only the interface methods and therefore is no implementation to display. Such classes may be viewed, in a clickable format using the Contract View or Interface View. }}
|
||||
{{note|This view is not available to .NET classes which are imported through by means of an assembly. This is because the assembly .exe or .dll exposes only the interface methods and therefore is no implementation to display. Such classes may be viewed, in a clickable format using the Contract View or Interface View. }}
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
The clients view [[Image:class-clients-icon]] displays all the classes which are using features of the current class, and thus rely on its [[Flat Contract view|interface]] . <br/>
|
||||
It is available through the '''Class''' tab of the [[EiffelStudio window overview|context tool]] .
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Suppliers|Suppliers]] <br/>
|
||||
[[Callers|Feature callers]] }}
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@
|
||||
[[Property:uuid|e8bbc475-d7f8-baa6-aba8-021c0e05c4b6]]
|
||||
The contract view [[Image:view-contracts-icon]] displays the contracts of all written-in features of the current class. It is available either through the [[EiffelStudio Editor|editor]] or through the '''Class''' tab of the [[EiffelStudio window overview|context tool]] .
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Flat Contract view|Flat contract view]] }}
|
||||
|
||||
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
The descendants view [[Image:class-descendents-icon]] displays all the classes which inherit from the current class,directly or not, using a tree-like indented layout. <br/>
|
||||
It is available through the '''Class''' tab of the [[EiffelStudio window overview|context tool]] .
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Ancestors|Ancestors]] }}
|
||||
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ The Flat Contract view [[Image:view-flat-contracts-icon]] displays the contract
|
||||
|
||||
{{warning| '''Caution''': For classes with many [[Ancestors|ancestors]] , computation of the Flat Contract view may require a few seconds. }}
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Class formatters: Flat view|Flat view]] <br/>
|
||||
[[Contract view|Contract view]] }}
|
||||
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
The routines view [[Image:class-features-routine-icon]] displays all the routine signatures of the current class, including inherited routines. <br/>
|
||||
It is available through the '''Class''' tab of the [[EiffelStudio window overview|context tool]] .
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Attributes|Attributes]] }}
|
||||
|
||||
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
The suppliers view [[Image:class-supliers-icon]] displays all the classes from which the current class is calling features. <br/>
|
||||
It is available through the '''Class''' tab of the [[EiffelStudio window overview|context tool]] .
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Clients|Clients]] }}
|
||||
|
||||
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
[[Property:uuid|ca7f840d-30fb-c1cb-8f2f-6b45aa244f95]]
|
||||
The ancestor view [[Image:feature-ancestors-icon]] displays all the features which the current feature is redefining.
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Descendant versions|Descendant versions]] }}
|
||||
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ It does not work with [[Breakpoints|breakpoints]] ; in order to do this the [[Fe
|
||||
|
||||
'''Note''': This view is not available to .NET features which are imported through by means of an assembly. This is because the assembly .exe or .dll exposes only the interface methods and therefore is no feature implementation to display. The feature interface may be viewed, in a clickable format using the Flat View.
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Class formatters: Basic text view|Class basic text view]] }}
|
||||
|
||||
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
[[Property:uuid|63b7a88c-86ff-7aef-bf31-05d0ed850e4e]]
|
||||
The callers view [[Image:feature-callers-icon]] display all the features which are calling the current feature. It is possible to choose in the preferences if callers of the descendants should be displayed too (they are by default).
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Clients|Class clients view]] }}
|
||||
|
||||
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
[[Property:uuid|c232a74a-7264-c8e1-4613-a65d75302602]]
|
||||
The descendant view [[Image:feature-descendents-icon]] displays all the features that redefine the current feature.
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Ancestor versions|Ancestor versions]] }}
|
||||
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@
|
||||
[[Property:uuid|b325d97c-772d-8207-a901-a401c6a61376]]
|
||||
The clickable view [[Image:view-clickable-feature-icon]] displays the feature body as it is seen at run-time (according to ancestor versions, if any). This is why it is possible to add or remove [[Breakpoints|breakpoints]] in this view.
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Class formatters: Flat view|Class flat view]] }}
|
||||
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ The homonyms view [[Image:feature-homonyms-icon]] displays all the features in
|
||||
|
||||
{{warning| '''Caution''': This operation may take a long time if the system has a lot of classes. }}
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Implementers|Implementers]] }}
|
||||
|
||||
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
[[Property:uuid|4032bef0-39e5-5fa6-0ffe-156392c0234e]]
|
||||
The implementers view [[Image:feature-implementers-icon]] displays all the different versions of the current feature by exploring the [[Ancestor versions|ancestor versions]] and the [[Descendant versions|descendant versions]] , and selecting among those the ones which are not inherited.
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Ancestor versions|Ancestor versions]] <br/>
|
||||
[[Descendant versions|Descendant versions]] }}
|
||||
|
||||
|
||||
@@ -25,7 +25,7 @@ After running the metric, you should see the following result in the Detailed Re
|
||||
|
||||
[[Image:domain-example2|Metric detailed result]]
|
||||
|
||||
{{note|Note: an element can appear more than one time in a domain, but the detailed result list show only distinct items, so it is possible that the calculated metric value is not equal to the number of items in the detailed result list.}}
|
||||
{{note|an element can appear more than one time in a domain, but the detailed result list show only distinct items, so it is possible that the calculated metric value is not equal to the number of items in the detailed result list.}}
|
||||
|
||||
|
||||
A domain can be used as an argument of a relation criterion, see the following example:
|
||||
@@ -52,10 +52,10 @@ And when this metric is calculated over input domain {<eiffel>APPLICATION</eiffe
|
||||
|
||||
[[Image:domain-example6|Actual semantic for input domain item]]
|
||||
|
||||
{{note|Note: Only code element target, group, folder, class, feature, delayed item, input domain item and application target can be specified through domain selector in Metrics tool. And code element generic, assertion, argument, local, line cannot be specified in domain selector, but they may present in the detailed result domain list.}}
|
||||
{{note|Only code element target, group, folder, class, feature, delayed item, input domain item and application target can be specified through domain selector in Metrics tool. And code element generic, assertion, argument, local, line cannot be specified in domain selector, but they may present in the detailed result domain list.}}
|
||||
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Units|Units]] <br/>
|
||||
[[Scopes|Scopes]] }}
|
||||
|
||||
|
||||
@@ -25,7 +25,7 @@ By convention, this definition treats as process metric as a composite metric in
|
||||
|
||||
The classification introduced for metrics extends to measures, so that we may talk about an elementary product measure, a composite process measure and so on.
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Attributes, metrics and measures|Metrics]] <br/>
|
||||
[[Scopes|Scopes]] <br/>
|
||||
[[Domains|Domains]] <br/>
|
||||
|
||||
@@ -18,7 +18,7 @@ This note does not introduce a metric theory, but defines a metric framework by
|
||||
|
||||
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Attributes, metrics and measures|Attributes, metrics and measures]] }}
|
||||
|
||||
|
||||
|
||||
@@ -37,7 +37,7 @@ This criterion independence principle is not absolute, however, and in some case
|
||||
|
||||
A metric is either elementary or composite. An elementary metric is either a raw metric, such as "number of features", or a derived metric obtained from slicing a raw metric by selection criteria. Composite metrics are obtained from existing metrics (elementary, or previously defined composite metrics) by applying some mathematical formula.
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Elementary and composite metrics|Elementary metrics]] <br/>
|
||||
[[Selection Criteria|Selection Criteria]] <br/>
|
||||
[[Criterion References|Selection criterion reference]] <br/>
|
||||
|
||||
@@ -111,7 +111,7 @@ There are three criterion connectors: and, or, not. They are self-explanatory. J
|
||||
|
||||
[[Image:selection-cri8|Relation criterion]]
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Domains|Domains]] <br/>
|
||||
[[Criterion References|Selection criterion reference]] }}
|
||||
|
||||
|
||||
@@ -3,9 +3,9 @@
|
||||
[[Property:uuid|f2d63c29-6be2-b3d9-a735-b18e08c5a678]]
|
||||
For functions and procedures, you can build a formal argument list. You can do this by clicking on the '''New argument''' button as many times as you need arguments.
|
||||
|
||||
{{note| '''Note''': Even though this dialog always shows parentheses, they are not generated if the list is empty (Eiffel's command-query separation (CQS) principle). }}
|
||||
{{note|Even though this dialog always shows parentheses, they are not generated if the list is empty (Eiffel's command-query separation (CQS) principle). }}
|
||||
<div> [[Image:feature-wizard-3-arguments]] </div>
|
||||
{{note| '''Note''': If you add arguments to a routine, it is not possible anymore to select routine type '''once'''. }}
|
||||
{{note|If you add arguments to a routine, it is not possible anymore to select routine type '''once'''. }}
|
||||
|
||||
For every attribute you selected, enter a name in the text box and a type using the [[Type selection|type selection]] .
|
||||
<div> [[Image:feature-wizard-1-argument]] </div>
|
||||
|
||||
@@ -6,7 +6,7 @@ The feature you create will be inserted in the feature clause you specified. If
|
||||
The export status is the class the feature is accessible for. Usually, this is <eiffel>ANY</eiffel> for public features, or <eiffel>NONE</eiffel> for implementation features, but you can specify any class here.
|
||||
[[Image:feature-wizard-export]]
|
||||
|
||||
{{note| '''Note''': In the class text, you can export a feature to more than one class but (for simplicity) not with this dialog. }}
|
||||
{{note|In the class text, you can export a feature to more than one class but (for simplicity) not with this dialog. }}
|
||||
|
||||
==Feature clause names==
|
||||
For feature clause names it is recommended that you pick one from the standard ones, but it is also possible to create a new one. If you have introduced a special feature clause name in your project, add it to the feature clause order list in the [[Preferences Reference|preferences]] and it will also appear in this dialog.
|
||||
|
||||
@@ -3,7 +3,7 @@
|
||||
[[Property:uuid|850bd867-5cbf-34d0-f94c-97a75bfa244b]]
|
||||
The feature name field is a text box that lets you enter a name for the feature. For help on how to choose the right name for a feature, see: [http://www.eiffel.com/doc/oosc/ Object-Oriented Software Construction, Second Edition] , paragraph 26.2.
|
||||
|
||||
{{warning| '''Warning''': EiffelStudio performs no validation on the name you choose. For example if you type a space in it, it will generate the code, and detect a syntax error only when compiling. }}
|
||||
{{warning|EiffelStudio performs no validation on the name you choose. For example if you type a space in it, it will generate the code, and detect a syntax error only when compiling. }}
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -5,14 +5,14 @@ Whenever you need to give a type of something in the dialog, the type selection
|
||||
<div> [[Image:feature-wizard-typeselection]] </div>
|
||||
When you select a class that is in the system and has formal generic parameters, the type selection component lets you specify an actual generic parameter in another type selection.
|
||||
<div> [[Image:feature-wizard-generictype]] </div>
|
||||
{{note| '''Note''': the window might grow in size because of the added component. }}
|
||||
{{note|the window might grow in size because of the added component. }}
|
||||
|
||||
Since the actual generic type selection is also a type selection, you can select another class with generic parameters and nest them as deep as you need.
|
||||
<div> [[Image:feature-wizard-generictyperec]] </div>
|
||||
You can also select the type <eiffel>TUPLE</eiffel>, which is a special class that can have zero or more generic parameters. When you select it, it has no parameters, but you can add one by clicking on the '''Add parameter''' button. Click it as often as the number of generic parameters that you need.
|
||||
<div> [[Image:feature-wizard-tupletype2]] <br/>
|
||||
</div>
|
||||
{{warning| '''Warning''': if you need a very complex type, it is better not to use the dialog, as the window might grow bigger than your screen. After you completed the feature, edit it manually in the class text. }}
|
||||
{{warning|if you need a very complex type, it is better not to use the dialog, as the window might grow bigger than your screen. After you completed the feature, edit it manually in the class text. }}
|
||||
|
||||
The code generated for the selected type is quite straightforward, an example:
|
||||
<div> [[Image:feature-wizard-complextype]] <br/>
|
||||
|
||||
@@ -43,7 +43,7 @@ As in Eiffel, -- introduces a comment, which has no effect on the specification.
|
||||
<br/>
|
||||
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Select a Run-time information record to generate the Execution Profile|Select a Run-time information record to generate the Execution Profile]] <br/>
|
||||
[[Profiling|How to profile a system]] }}
|
||||
|
||||
|
||||
@@ -7,7 +7,7 @@
|
||||
# [[Select the information you need and formulate your query|'''Final step''': Select the information you need and formulate your query.]]
|
||||
# [[Profile query window|Profile query window]]
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Profiler wizard: Introduction|How the Profiler wizard works]] <br/>
|
||||
[[Profiling|How to profile a system]] }}
|
||||
|
||||
|
||||
@@ -13,11 +13,11 @@ To change the operator affecting an existing sub query, select it in either the
|
||||
|
||||
Click on the '''Save''' button to save the currently displayed results in a text file.
|
||||
|
||||
{{tip| '''Tip''': To visualize the result in Microsoft Excel or any other spreadsheet, select the entire text (except the first three lines where the Execution Profile file is specified), copy it and then paste it into Excel. }}
|
||||
{{tip|To visualize the result in Microsoft Excel or any other spreadsheet, select the entire text (except the first three lines where the Execution Profile file is specified), copy it and then paste it into Excel. }}
|
||||
<br/>
|
||||
[[Image:profiler-query-window]] <br/>
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Profiler wizard: Introduction|How the Profiler wizard works]] <br/>
|
||||
[[Profiling|How to profile a system]] }}
|
||||
|
||||
|
||||
@@ -5,12 +5,12 @@ The second screen of the wizard lets you reuse a previously generated ''Executio
|
||||
|
||||
The profiler wizard has detected that one or more ''Execution Profiles'' have already been generated for this system in this compilation mode. If you have executed your system after the generation of the existing profile, select '''Generate a profile from Run-time information record''' to create a new ''Execution Profile'' for the newly produced ''Run-time information record''.
|
||||
|
||||
{{note| '''Note''': If you choose '''Generate a profile from Run-time information record''' the generated ''Execution Profile'' will be written into ''<project_directory>/EIFGENa/target_name/W_CODE/profinfo.pfi'' if you have selected '''Workbench mode''' in the first step, or ''<project_directory>/EIFGENs/target_name/F_CODE/profinfo.pfi'' if you have selected '''Finalized mode'''. If a file with the same name already exists its content will be destroyed and replaced. }}
|
||||
{{note|If you choose '''Generate a profile from Run-time information record''' the generated ''Execution Profile'' will be written into ''<project_directory>/EIFGENa/target_name/W_CODE/profinfo.pfi'' if you have selected '''Workbench mode''' in the first step, or ''<project_directory>/EIFGENs/target_name/F_CODE/profinfo.pfi'' if you have selected '''Finalized mode'''. If a file with the same name already exists its content will be destroyed and replaced. }}
|
||||
<br/>
|
||||
|
||||
However, if you have not executed your system since the generation of the last ''Execution Profile'', there is no need to generate a new ''Execution Profile''. If you are in the latter case, select '''Use existing profile''' and choose the last ''Execution Profile'' you have generated.
|
||||
|
||||
{{tip| '''Tip''': If you want to archive different ''Execution Profiles'' (to compare them for example), rename the ''profinfo.pfi'' file into a new name but keep the .pfi extension. The profiler wizard detects existing Execution Profiles by checking the file extensions. }}
|
||||
{{tip|If you want to archive different ''Execution Profiles'' (to compare them for example), rename the ''profinfo.pfi'' file into a new name but keep the .pfi extension. The profiler wizard detects existing Execution Profiles by checking the file extensions. }}
|
||||
<br/>
|
||||
[[Image:profiler-wizard-second-state]] <br/>
|
||||
<br/>
|
||||
@@ -18,7 +18,7 @@ However, if you have not executed your system since the generation of the last '
|
||||
Clicking '''Next''' will lead you to the [[Select a Run-time information record to generate the Execution Profile|Third state]] if you have selected '''Generate a profile from Run-time information record'''. On the other hand if you have selected '''Use existing profile''' you will go to the [[Select the information you need and formulate your query|Final state]] .
|
||||
<br/>
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Profiler wizard: Introduction|How the Profiler wizard works]] <br/>
|
||||
[[Profiling|How to profile a system]] }}
|
||||
|
||||
|
||||
@@ -11,7 +11,7 @@ If you have run a finalized system under the control of the profiler then select
|
||||
Clicking '''Next''' will lead you to the [[Reuse or Generate an Execution Profile|Second state]] or to the [[Select a Run-time information record to generate the Execution Profile|Third state]] depending on whether an ''Execution Profile'' has already been generated for this compilation mode or not. If no ''Execution Profile'' has been generated so far (which happens the first time you execute this wizard for a specified project in a given compilation mode) you will go to the [[Select a Run-time information record to generate the Execution Profile|Third state]] , otherwise you will go to the [[Reuse or Generate an Execution Profile|Second state]] .
|
||||
<br/>
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Profiler wizard: Introduction|How the profiler wizard works]] [[Profiling|How to profile a system]] }}
|
||||
|
||||
|
||||
|
||||
@@ -50,7 +50,7 @@ Each sub-query must have the following syntax 'attribute operator value' where:
|
||||
Clicking '''Next''' will open the [[Profile query window|Profile query window]] and display the results of the formulated query.
|
||||
<br/>
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Profiler wizard: Introduction|How the Profiler wizard works]] <br/>
|
||||
[[Profiling|How to profile a system]] }}
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ The third screen of the wizard lets you generate an ''Execution Profile'' from a
|
||||
|
||||
Then, in the combo box labeled '''Profiler used to produce the above record''', select the profiler that has been used to produce the ''Run-time information record'' you have entered. If the profiler used to execute the system does not appear in the combo box, you have to add it. See [[How to set up a Profiler Configuration File|How to set up a Profiler Configuration File]] for more details on how to do so.
|
||||
|
||||
{{note| '''Note''': ''The Run-time information record'' has to be located in the ''EIFGENs/target_name/W_code'' directory of your project. }}
|
||||
{{note|The Run-time information record'' has to be located in the ''EIFGENs/target_name/W_code'' directory of your project. }}
|
||||
|
||||
<br/>
|
||||
[[Image:profiler-wizard-third-state]] <br/>
|
||||
@@ -17,7 +17,7 @@ Clicking '''Next''' will lead you to the [[Select the information you need and f
|
||||
[[Image:profiler-wizard-rtir-error-state]] <br/>
|
||||
<br/>
|
||||
|
||||
{{seealso| '''See Also''' <br/>
|
||||
{{seealso|<br/>
|
||||
[[Profiler wizard: Introduction|How the Profiler wizard works]] <br/>
|
||||
[[Profiling|How to profile a system]] <br/>
|
||||
[[How to set up a Profiler Configuration File|How to set up a Profiler Configuration File]] }}
|
||||
|
||||
Reference in New Issue
Block a user