diff -r 5072524fcc79 -r 80ef3a206772 Symbian3/PDK/Source/GUID-7767599C-7B77-5DD1-8E3E-7AD01EC6F6A1.dita --- a/Symbian3/PDK/Source/GUID-7767599C-7B77-5DD1-8E3E-7AD01EC6F6A1.dita Fri Jul 02 12:51:36 2010 +0100 +++ b/Symbian3/PDK/Source/GUID-7767599C-7B77-5DD1-8E3E-7AD01EC6F6A1.dita Fri Jul 16 17:23:46 2010 +0100 @@ -29,7 +29,7 @@ aStream << iData; aStream << *iCompA; aStream << *iCompB; - }
The stream can be visualised as:
Storing a compound object’s component objects out-of-line means writing all of its component objects to a different stream from that to which it, itself, is written. Each component may be written to its own stream or to its own network of streams. The main advantage of this is that it allows for deferred loading of streams.
It is important to note that components are stored before the containing object.
The following code fragment defines an example class, CCompound, having two components,
The stream can be visualised as:
Storing a compound object’s component objects out-of-line means writing all of its component objects to a different stream from that to which it, itself, is written. Each component may be written to its own stream or to its own network of streams. The main advantage of this is that it allows for deferred loading of streams.
It is important to note that components are stored before the containing object.
The following code fragment defines an example class, CCompound, having two components,
The
writes the
writes
returns the ID of the top-level stream.
This can be visualised as:
and implemented as:
The
writes the
writes
returns the ID of the top-level stream.
This can be visualised as:
and implemented as: