From a5e9c265c6af644dc7c15f7b456287749f738d38 Mon Sep 17 00:00:00 2001 From: halw Date: Sat, 7 Apr 2012 12:46:23 +0000 Subject: [PATCH] Changed `independent_store' from a `future' feature to currently existing. Author:halw Date:2012-04-07T12:46:23.000000Z git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@1064 abb3cda0-5349-4a8f-a601-0c33ac3a8c38 --- .../eiffelbase/eiffelbase-tutorial/eiffelbase-kernel.wiki | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/current/solutions/basic-computing/eiffelbase/eiffelbase-tutorial/eiffelbase-kernel.wiki b/documentation/current/solutions/basic-computing/eiffelbase/eiffelbase-tutorial/eiffelbase-kernel.wiki index fc517fba..5e656ca5 100644 --- a/documentation/current/solutions/basic-computing/eiffelbase/eiffelbase-tutorial/eiffelbase-kernel.wiki +++ b/documentation/current/solutions/basic-computing/eiffelbase/eiffelbase-tutorial/eiffelbase-kernel.wiki @@ -358,7 +358,7 @@ Although basic_store and other procedures of [[ref:/libraries/base/reference/sto ==Varieties of store operations== Two variants of the store operation are supported: basic store and general store. Basic store produces more compact structures in the resulting files, and is slightly faster; but the resulting structure is dependent on the system which executes the store operation ('System' is taken here, as elsewhere in this documentation, in its Eiffel sense of an executable assembly of classes, compiled together with the help of a configuration file.) This means that you can use procedure basic_store to store an object structure during an execution of a system if you will only retrieve it later in that execution, or in a
-subsequent execution of the same system. If you need to store objects from a certain system and then retrieve them from a different system, possibly running on a different computer, use general_store. The result of general_store is still platform-dependent; the representation of numbers, in particular, is determined by the underlying machine architecture. A third variant called independent_store will be added in the future to [[ref:/libraries/base/reference/storable_chart|STORABLE]] , using an entirely platform-independent storage format; then a system running on a computer with a certain architecture will be able to retrieve, without any explicit conversion operation, object structures stored by a system running on a machine of a completely different architecture. With general_store the storing and retrieving computers must have compatible architectures. +subsequent execution of the same system. If you need to store objects from a certain system and then retrieve them from a different system, possibly running on a different computer, use general_store. The result of general_store is still platform-dependent; the representation of numbers, in particular, is determined by the underlying machine architecture. A third variant called independent_store, uses an entirely platform-independent storage format; independent_store allows a system running on a computer with a certain architecture to retrieve, without any explicit conversion operation, object structures stored by a system running on a machine of a completely different architecture. With general_store the storing and retrieving computers must have compatible architectures. ==Retrieval==