mirrors/eiffel-org
1
0
Fork 0
mirror of https://github.com/EiffelSoftware/eiffel-org.git synced 2025-12-08 15:52:26 +01:00
Code Issues Packages Projects Releases Wiki Activity

Added links to references to Eiffel: The Language

Browse Source 
Author:halw
Date:2009-12-21T23:09:51.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@377 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
halw
2009-12-21 23:09:51 +00:00
parent e00fdd689c
commit efbf54dba5
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
documentation/current/solutions/basic-computing/eiffelbase/eiffelbase-tutorial/eiffelbase-kernel.wiki
View File

@@ -108,7 +108,7 @@ Function default also has an empty body; its result type is <code>like Current</
=Language-related Facilities=
A number of classes offer facilities which are very close to the language level. Here too the book ''Eiffel: The Language'' covers the classes in detail, so we can satisfy ourselves with a quick summary; the flat-short forms appear in part C.
A number of classes offer facilities which are very close to the language level. Here too the book ''[[Eiffel: The Language]]'' covers the classes in detail, so we can satisfy ourselves with a quick summary; the flat-short forms appear in part C.
==Basic types==
@@ -345,7 +345,7 @@ Class [[ref:/libraries/base/reference/storable_chart|STORABLE]] addresses this
==Persistence completeness==
A fundamental requirement on object persistence mechanisms is the '' Persistence Completeness'' rule, stated as follows in ''Eiffel: The Language'': <br/>
A fundamental requirement on object persistence mechanisms is the '' Persistence Completeness'' rule, stated as follows in ''[[Eiffel: The Language]]'': <br/>
Whenever a routine of class [[ref:/libraries/base/reference/storable_chart|STORABLE]] stores an object into an external file, it stores with it the dependents of that object. Whenever one of the associated retrieval routines retrieves a previously stored object, it also retrieves all its dependents. <br/>
Storing an object just by itself would usually result in wrong semantics: most objects contain references to other objects, which must also be stored and retrieved with it. The persistence completeness rule ensures that this is always the case. It also means, of course, that the features of [[ref:/libraries/base/reference/storable_chart|STORABLE]] must do much more than simple input and output; they must perform complete traversals of object structures.