mirror of
https://github.com/EiffelSoftware/eiffel-org.git
synced 2025-12-06 14:52:03 +01:00
Author:halw
Date:2008-09-30T20:05:39.000000Z git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@66 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
@@ -1,11 +1,6 @@
|
||||
[[Property:title|Community]]
|
||||
[[Property:weight|2]]
|
||||
[[Property:uuid|75c75712-7c3e-2757-51b7-77b404471e2e]]
|
||||
== Community contributions ==
|
||||
The Community book is a vehicle through which community members will be able to submit and/or revise documentation content.
|
||||
|
||||
It is here that you will find references to valuable work done by and available to the Eiffel community.
|
||||
|
||||
* [http://www.gobosoft.com/ Gobo Tools and Libraries]
|
||||
|
||||
* [http://sourceforge.net/projects/safe Software App Foundations in Eiffel] (SAFE)
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
[[Property:title|19 APPENDIX: WRITING DOCUMENTATION FILTERS WITH EFF, THE EIFFEL FILTER FORMAT]]
|
||||
[[Property:title|19 Appendix: Writing Documentation Filters with EFF, the Eiffel Filter Format]]
|
||||
[[Property:link_title|Appendix: Writing Documentation Filters with EFF, the Eiffel Filter Format]]
|
||||
[[Property:weight|6]]
|
||||
[[Property:uuid|0d17d433-3d4f-9575-49f7-d97eccb1a5b1]]
|
||||
@@ -119,8 +119,3 @@ If <code> c </code> is not one of the characters for which special conventions h
|
||||
|
||||
A multi-line entry uses the Eiffel convention for string continuations: <code> % </code> at the end of a line to signal that there is a continuation; a continuation line begins with zero or more spaces and tabs followed by a <code> % </code> ; the characters after the <code> % </code> are the continuation of the string.
|
||||
|
||||
[[18 EXECUTING A SYSTEM WITHIN AND WITHOUT EIFFELSTUDIO|<< Previous]]
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
[[Property:title|9 BROWSING FEATURES]]
|
||||
[[Property:title|9 Browsing Features]]
|
||||
[[Property:link_title|Browsing Features]]
|
||||
[[Property:weight|-6]]
|
||||
[[Property:uuid|2c0b0a6c-08e8-fdbc-1eab-e2d87b01ce48]]
|
||||
@@ -72,8 +72,4 @@ The last button, <code> Homonyms </code>, displays all the features of the syste
|
||||
|
||||
In any system or library that takes advantage of inheritance and its associated mechanisms -- renaming, redefinition, effecting, undefinition, multiple and repeated inheritance, polymorphism, dynamic binding -- the feature browsing facilities that we have just explored are invaluable to track what happens to features. What makes them even more precious is their connection with the rest of the browsing and documentation capabilities, especially the pick-and-drop which we will now study.
|
||||
</div>
|
||||
[[8 PRODUCING AND EXPORTING DOCUMENTATION|<< Previous]] [[10 RETARGETING THROUGH PICK-AND-DROP|Next >>]]
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
[[Property:title|17 THE COMMAND-LINE COMPILER]]
|
||||
[[Property:title|17 The Command-Line Compiler]]
|
||||
[[Property:link_title|The Command-Line Compiler]]
|
||||
[[Property:weight|4]]
|
||||
[[Property:uuid|62bd8d62-a734-3ec0-9533-eaa096e7b81f]]
|
||||
@@ -13,8 +13,3 @@ To use the command-line compiler -- <code> ec </code> for Eiffel Compilation --
|
||||
|
||||
Specify <code> class_name </code> and <code> feature_name </code> only if you wish to produce information about a class or a feature. Otherwise <code> ec </code> will compile a system according to each specified <code> option </code>. [[EiffelStudio: Command line options|Click here to see the set of supported options.]]
|
||||
|
||||
[[16 HOW EIFFELSTUDIO COMPILES|<< Previous]] [[18 EXECUTING A SYSTEM WITHIN AND WITHOUT EIFFELSTUDIO|Next >>]]
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
[[Property:title|4 COMPILING AND EXECUTING A SYSTEM]]
|
||||
[[Property:title|4 Compiling and Executing a System]]
|
||||
[[Property:link_title|Compiling and Executing a System]]
|
||||
[[Property:weight|-12]]
|
||||
[[Property:uuid|58494be3-f29f-3a15-a27e-e635bdc71c53]]
|
||||
@@ -50,8 +50,3 @@ The message " <code> Press Return to finish the execution </code>" would not app
|
||||
|
||||
If before closing the console window you look at the main EiffelStudio window (by moving away the console window) you will notice that it looks different from before, since it now shows the fields useful in monitoring execution and debugging. But we'll look at this later. For the moment just dismiss the console by following the advice to " <code> Press Return </code>": hit the Return or Enter key.
|
||||
|
||||
[[2 COPYING THE EXAMPLE FILES|<< Previous]] [[5 A LOOK AT THE PROJECT DIRECTORY|Next >>]]
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
[[Property:title|14 COMPUTING PROJECT METRICS]]
|
||||
[[Property:title|14 Computing Project Metrics]]
|
||||
[[Property:link_title|Computing Project Metrics]]
|
||||
[[Property:weight|0]]
|
||||
[[Property:uuid|8d1a3556-d9a2-0ac8-4d54-458f18cb56ad]]
|
||||
@@ -43,6 +43,3 @@ A metric can be computed over a scope, this scope is defined using a domain. In
|
||||
* [[Metric History Panel|Metric History panel]]
|
||||
* [[Metric Archive Panel|Metric Archive panel]]
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
[[Property:title|2 COPYING THE EXAMPLE FILES]]
|
||||
[[Property:title|2 Copying the Example Files]]
|
||||
[[Property:link_title|Copying the Example Files]]
|
||||
[[Property:weight|-14]]
|
||||
[[Property:uuid|bb8ff7d7-2e93-d150-339c-d9afb967bc98]]
|
||||
@@ -23,8 +23,3 @@ The final executable generated through " ''finalization''" (optimized compilatio
|
||||
|
||||
Without precompiled EiffelBase you would need about 3.5 megabytes, plus about 25 megabytes of generated C code and auxiliary files. The executable in that case will take up about 250 kilobytes.
|
||||
|
||||
[[1 OVERVIEW AND PREREQUISITES|<< Previous]] [[3 STARTING EIFFELSTUDIO AND OPENING A PROJECT|Next >>]]
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
[[Property:title|13 DEBUGGING AND RUN-TIME MONITORING]]
|
||||
[[Property:title|13 Debugging and Run-time Monitoring]]
|
||||
[[Property:link_title|Debugging and Run-time Monitoring]]
|
||||
[[Property:weight|-2]]
|
||||
[[Property:uuid|a53f6a74-7145-35ab-ed5e-2905aeb88774]]
|
||||
@@ -96,8 +96,4 @@ In debugging sessions for more advanced applications, you will also find self-ex
|
||||
|
||||
The combination of these facilities provides you with a level of <span>dynamic</span> information on the execution of your system that matches the <span>static</span> information that the browsing mechanisms studied in preceding sections provide about the system's structure.
|
||||
</div>
|
||||
[[12 HANDLING SYNTAX AND VALIDITY ERRORS|<< Previous]] [[14 COMPUTING PROJECT METRICS|Next >>]]
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
[[Property:title|18 EXECUTING A SYSTEM WITHIN AND WITHOUT EIFFELSTUDIO]]
|
||||
[[Property:title|18 Executing a System Within and Without EiffelStudio]]
|
||||
[[Property:link_title|Executing a System Within and Without EiffelStudio]]
|
||||
[[Property:weight|5]]
|
||||
[[Property:uuid|8256398e-d1a9-0471-664a-3225c7dfb306]]
|
||||
@@ -40,8 +40,4 @@ A system compiled in "Workbench mode" -- frozen or melted -- is normally meant f
|
||||
|
||||
With this discussion of compilation and execution we have finished our review of the key capabilities of EiffelStudio. Not everything has been covered, but you are now familiar with the essentials and ready to discover the rest by yourself, both by trying out various capabilities -- most of which should be self-explanatory -- and examining the extensive online documentation that accompanies the product.
|
||||
</div>
|
||||
[[17 THE COMMAND-LINE COMPILER|<< Previous]] [[19 APPENDIX: WRITING DOCUMENTATION FILTERS WITH EFF, THE EIFFEL FILTER FORMAT|Next >>]]
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
[[Property:title|15 GRAPHICS-BASED DESIGN]]
|
||||
[[Property:title|15 Graphics-based Design]]
|
||||
[[Property:link_title|Graphics-based Design]]
|
||||
[[Property:weight|1]]
|
||||
[[Property:uuid|78239225-67a7-8718-857d-f2c8fb70ef18]]
|
||||
@@ -140,8 +140,4 @@ It's for class diagrams that the <code> Relation depth </code> button is most in
|
||||
<div> [[Image:index-139]] [[general/guided_tour/studio/index-139.png|(link)]] </div>
|
||||
This will conclude our review of the Diagram facilities of EiffelStudio, although you'll surely discover some further riches by yourself and through the rest of the documentation. We hope the complete seamlessness between text and pictures will enable you to increase the effectiveness of your analysis work, or your design work, or your programming -- whatever level of system development you need to tackle.
|
||||
</div>
|
||||
[[14 COMPUTING PROJECT METRICS|<< Previous]] [[16 HOW EIFFELSTUDIO COMPILES|Next >>]]
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
[[Property:title|12 HANDLING SYNTAX AND VALIDITY ERRORS]]
|
||||
[[Property:title|12 Handling Syntax and Validity Errors]]
|
||||
[[Property:link_title|Handling Syntax and Validity Errors]]
|
||||
[[Property:weight|-3]]
|
||||
[[Property:uuid|c2be8123-b793-f8ce-e082-d4fdacc6bbe6]]
|
||||
@@ -62,8 +62,4 @@ The rule has several clauses, numbered. Since the error message showed the error
|
||||
|
||||
To correct the error the easiest is to go back to class <code> TESTROOT </code> and reinstate the comment symbol <code> -- </code> (two consecutive dashes) on the erroneous line. Save and compile to continue with a valid system.
|
||||
</div>
|
||||
[[11 RECOMPILING AND EDITING|<< Previous]] [[13 DEBUGGING AND RUN-TIME MONITORING|Next >>]]
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
[[Property:title|16 HOW EIFFELSTUDIO COMPILES]]
|
||||
[[Property:title|16 How EiffelStudio Compiles]]
|
||||
[[Property:link_title|How EiffelStudio Compiles]]
|
||||
[[Property:weight|3]]
|
||||
[[Property:uuid|6fc86303-8afe-78af-6ca7-2853e8bfcbc3]]
|
||||
@@ -184,8 +184,4 @@ Note that cross-development does not <span>require</span> finalization, since yo
|
||||
|
||||
Finalize the example system now by selecting the menu entry <code> Project </code> <code> --> </code> <code> Finalize </code>. Here too you will be asked to confirm, although the dialog enables you to suppress that confirmation for later attempts, and you may skip C compilation. You will note that finalization is longer than freezing, but still remains quite reasonable thanks to the extensive optimization of the Eiffel compilation process and the structure of the generated C code.
|
||||
</div>
|
||||
[[15 GRAPHICS-BASED DESIGN|<< Previous]] [[17 THE COMMAND-LINE COMPILER|Next >>]]
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
[[Property:title|5 A LOOK AT THE PROJECT DIRECTORY]]
|
||||
[[Property:title|5 A Look at the Project Directory]]
|
||||
[[Property:link_title|A Look at the Project Directory]]
|
||||
[[Property:weight|-11]]
|
||||
[[Property:uuid|d82eae3f-fe0d-3e27-008e-61afd05f8cb0]]
|
||||
@@ -25,8 +25,3 @@ You seldom need to look into <code> EIFGENs </code>, although you should know th
|
||||
|
||||
By the way, we are now done with any platform-specific instructions. Everything in the rest of this Tour, other than the graphical look-and-feel, will work the same across all EiffelStudio platforms.
|
||||
|
||||
[[4 COMPILING AND EXECUTING A SYSTEM|<< Previous]] [[6 STARTING TO BROWSE|Next >>]]
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,5 +1,4 @@
|
||||
[[Property:title|MANUAL IDENTIFICATION AND COPYRIGHT]]
|
||||
[[Property:link_title|Manual identification and copyright]]
|
||||
[[Property:title|Manual identification and copyright]]
|
||||
[[Property:weight|7]]
|
||||
[[Property:uuid|c581a81b-fc9b-99bd-e73a-f290f6051a45]]
|
||||
Title: ''EiffelStudio: A Guided Tour'', Eiffel Software Technical Report TR-EI-68/GT. (Replaces TR-EI-38/EB.)
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
[[Property:title|1 OVERVIEW AND PREREQUISITES]]
|
||||
[[Property:title|1 Overview and Prerequisites]]
|
||||
[[Property:link_title|Overview and Prerequisites]]
|
||||
[[Property:weight|-15]]
|
||||
[[Property:uuid|acf5433b-14e9-1d21-c8cf-997db7821550]]
|
||||
@@ -81,8 +81,3 @@ Please take a moment to locate the example files on your installation. They all
|
||||
|
||||
(Windows users: remember that instead of the slash <code> / </code> your platform uses a backslash <code> \ </code>. OpenVMS users: this is to be replaced by the OpenVMS path naming conventions.)
|
||||
|
||||
[[2 COPYING THE EXAMPLE FILES|Next >>]]
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
[[Property:title|8 PRODUCING AND EXPORTING DOCUMENTATION]]
|
||||
[[Property:title|8 Producing and Exporting Documentation]]
|
||||
[[Property:link_title|Producing and Exporting Documentation]]
|
||||
[[Property:weight|-7]]
|
||||
[[Property:uuid|ca43a3c2-9e1a-a69f-81cf-55d0b12294ea]]
|
||||
@@ -162,8 +162,3 @@ Although we suggest staying with the standard, you can easily change any convent
|
||||
|
||||
The documentation generation mechanisms, using HTML or other formats, let you publish your designs, at the level of detail you desire, on an Intranet, the Internet, or as part of documents you release. They are an important part of the power of EiffelStudio for quality software development.
|
||||
|
||||
[[7 CLASS VIEWS|<< Previous]] [[9 BROWSING FEATURES|Next >>]]
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
[[Property:title|11 RECOMPILING AND EDITING]]
|
||||
[[Property:title|11 Recompiling and Editing]]
|
||||
[[Property:link_title|Recompiling and Editing]]
|
||||
[[Property:weight|-4]]
|
||||
[[Property:uuid|6574a573-48b9-6088-aa98-53d7119d7c5c]]
|
||||
@@ -131,8 +131,4 @@ Several important text editors from various providers have '''Eiffel modes''', w
|
||||
* <span>Emacs</span> -- see www.emacs.org.
|
||||
* <span>Editeur</span>, a Windows syntax highlighting editor -- see www.studioware.com.
|
||||
</div></div>
|
||||
[[10 RETARGETING THROUGH PICK-AND-DROP|<< Previous]] [[12 HANDLING SYNTAX AND VALIDITY ERRORS|Next >>]]
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
[[Property:title|10 RETARGETING THROUGH PICK-AND-DROP]]
|
||||
[[Property:title|10 Retargeting Through Pick-and-Drop]]
|
||||
[[Property:link_title|Retargeting Through Pick-and-Drop]]
|
||||
[[Property:weight|-5]]
|
||||
[[Property:uuid|a3789781-153b-7f4d-bb94-4bdf8923fb56]]
|
||||
@@ -155,8 +155,3 @@ As a conclusion to this review of Pick-and-Drop let's recapitulate the various w
|
||||
| [[6 STARTING TO BROWSE|"Starting a new tool" in Chapter 6, "Starting To Browse".]]
|
||||
|}
|
||||
|
||||
[[9 BROWSING FEATURES|<< Previous]] [[11 RECOMPILING AND EDITING|Next >>]]
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
[[Property:title|6 STARTING TO BROWSE]]
|
||||
[[Property:title|6 Starting To Browse]]
|
||||
[[Property:link_title|Starting To Browse]]
|
||||
[[Property:weight|-10]]
|
||||
[[Property:uuid|cb6c2e52-d238-9b55-0b78-ab3af9568550]]
|
||||
@@ -138,8 +138,3 @@ The place where we found the class <code> CHAIN </code> in the original tool (th
|
||||
|
||||
While you are at it, try a couple of other ways to create a new Development Window. Go to <code> File </code> <code> --> </code> <code> New window </code> ; this creates a new tool, untargeted. The title bar says " <code> Empty development tool #1 </code> ". You can get the same effect by clicking the Create New Window icon, leftmost on the top row of buttons, just below " <code> File </code>". The corresponding keyboard accelerator is CTRL- <code> N </code>.
|
||||
|
||||
[[5 A LOOK AT THE PROJECT DIRECTORY|<< Previous]] [[7 CLASS VIEWS|Next >>]]
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
[[Property:title|3 STARTING EIFFELSTUDIO AND OPENING A PROJECT]]
|
||||
[[Property:title|3 Starting EiffelStudio and Opening a Project]]
|
||||
[[Property:link_title|Starting EiffelStudio and Opening a Project]]
|
||||
[[Property:weight|-13]]
|
||||
[[Property:uuid|676cf329-5640-69c4-d10b-b56fcd3f2ff9]]
|
||||
@@ -22,8 +22,4 @@ To launch EiffelStudio on Unix or OpenVMS, change directory to <code> YOURDIR </
|
||||
|
||||
In general you can start EiffelStudio from any directory, but to make things simple for this Tour '''please make sure''' indeed to execute the <code> estudio </code> command from <code> YOURDIR </code>. (This will allow us to use relative rather than absolute names for some of the files involved.)
|
||||
|
||||
[[2 COPYING THE EXAMPLE FILES|<< Previous]] [[4 COMPILING AND EXECUTING A SYSTEM|Next >>]]
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
[[Property:title|7 CLASS VIEWS]]
|
||||
[[Property:title|7 Class Views]]
|
||||
[[Property:link_title|Viewing Classes]]
|
||||
[[Property:weight|-9]]
|
||||
[[Property:uuid|78136af1-5d7a-f3d2-9619-17f4c0541f1e]]
|
||||
@@ -91,8 +91,3 @@ The remaining Class View buttons all display information in the same format. Eac
|
||||
* <code> External </code> features, implemented as calls to routines, macros or other elements implemented in other languages. <code> LIST </code> hasn't any.
|
||||
* <code> Exported </code> features: those available to all clients. <code> LIST </code> has quite a few.
|
||||
|
||||
[[6 STARTING TO BROWSE|<< Previous]] [[8 PRODUCING AND EXPORTING DOCUMENTATION|Next >>]]
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -4,18 +4,22 @@
|
||||
The first thing to do to start Eiffeling is to create a project. Most commands are disabled when no project is created.
|
||||
|
||||
When opening EiffelStudio, by default a dialog is popped up that proposes to create or open a project:
|
||||
[[Image:startup-dialog]]
|
||||
|
||||
[[Image:startup-dialog|center]]
|
||||
|
||||
Under '''Create project''', several options are offered, which depend on the platform you are on.
|
||||
* '''Basic application''' is the most basic new project that can be generated. It only includes the [[EiffelBase|base library]] and by default only creates the frame of the project. This is the ideal choice to start a textual (console) application, or to discover Eiffel. Indeed, the project is very light and includes only things that are essential in any project. It is available on all platforms.
|
||||
* '''.NET application''' has by default all essential components to start a project targeting the Microsoft .NET platform. Of course, it is only available on Windows, and only if you have chosen to install the .NET support during the installation.
|
||||
* '''Vision2 application''' creates a new project that includes the [[EiffelVision Introduction|Eiffel Vision2 library]] . This is the perfect choice to start a platform-independent graphic application, or even any graphic application, since EiffelVision2 is easier to use than platform-specific libraries. This option is available on all platforms.
|
||||
* '''WEL application''' generates a project using the [[WEL|Windows Eiffel Library(WEL)]] . This option is recommended for projects needing advanced Windows features, or Windows applications that are time-critical, since the graphic functionality provided by WEL is more efficient than the one provided by Vision2, which on the other hand provides a platform-independent abstract interface. This wizard is only available on Windows.
|
||||
All those options are also available in the ''' File'''/ '''New project...''' menu. This pops up a dialog with all the options to generate a new project: <br/>[[Image:create-a-project]]
|
||||
All those options are also available in the ''' File'''/ '''New project...''' menu. This pops up a dialog with all the options to generate a new project:
|
||||
|
||||
[[Image:create-a-project|center]]
|
||||
|
||||
{{tip|If you checked the "Don't show this dialog at startup" checkbox in the start-up dialog but want to get it back, you can use the [[Discardable dialogs|Preferences dialog]] to reset the default value. }}
|
||||
|
||||
|
||||
{{seealso|<br/>
|
||||
[[Retrieving a project from a configuration file|Retrieving a project from an configuration file]] }}
|
||||
{{seealso| [[Retrieving a project from a configuration file|Retrieving a project from an configuration file]] }}
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -32,7 +32,7 @@ Sources of information on Eiffel include:
|
||||
|
||||
:A summary of the arguments for using Eiffel.
|
||||
|
||||
===[[Method]] -- The Eiffel Method and Language===
|
||||
===[[Method|Method and Language]] -- The Eiffel Method and Language===
|
||||
|
||||
:Materials promoting the understanding of the Eiffel software development method and Eiffel the language.
|
||||
|
||||
@@ -44,13 +44,13 @@ Sources of information on Eiffel include:
|
||||
|
||||
:There are technologies available with Eiffel that provide solutions to many ordinary development needs ... and to some extraordinary needs, too. This book addresses these requirements and the Eiffel technologies that satisfy them.
|
||||
|
||||
===[[Windows]] -- Eiffel with Microsoft Windows===
|
||||
===[[Platform specifics]] -- Support for particular operating systems===
|
||||
|
||||
:Although the majority of Eiffel is completely platform independent, Eiffel does provide solutions for some development needs that are strictly related to Microsoft Windows. Those technologies are described in this book.
|
||||
:Although the majority of Eiffel is completely platform independent, Eiffel does provide solutions for some development needs that are strictly related to specific operating systems. Those technologies are described in this book.
|
||||
|
||||
===[[Community]] -- Community Contributions===
|
||||
|
||||
:Eiffel is a community. Developers have been using Eiffel to build high-quality software systems for many years. During that time, valuable software libraries and other assets have emerged, and their authors have been willing to share them with other Eiffel users for the greater good. This book contains information about those contributions.
|
||||
:Eiffel is a community. Members of the Eiffel community can contribute to this documentation through this book.
|
||||
|
||||
|
||||
----
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
[[Property:title|Platform specifics]]
|
||||
[[Property:weight|-5]]
|
||||
[[Property:uuid|fe9cb24b-3f0f-cb79-8ef0-27c34c851dfe]]
|
||||
|
||||
Although the majority of Eiffel is completely platform independent, Eiffel does provide solutions for some development needs that are strictly related to the capabilities of specific operating systems. This book documents Eiffel's facilities, tools, and libraries that are targeted to specific operation systems.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user