there is something confusing about the methods .dump, .load and .restore
within the Marshalling-Routines:
The Documentations says that with .dump a class could be stored on disk and
with .load it could be used as .new to create an object, but this is not
correct, only with the .restore method a new object could be created.
I tested this with ruby version 1.6.8 and 1.8.0 both same results.
If one works, the other should. They are synonyms.
···
On Fri, Mar 21, 2003 at 07:06:44AM +0900, feno7@gmx.de wrote:
Hello Dear Ruby-Users,
there is something confusing about the methods .dump, .load and .restore
within the Marshalling-Routines:
The Documentations says that with .dump a class could be stored on disk and
with .load it could be used as .new to create an object, but this is not
correct, only with the .restore method a new object could be created.
I tested this with ruby version 1.6.8 and 1.8.0 both same results.
I don’t understand what you are saying, please can you post an example which
demonstrates the problem?
‘restore’ is just a synonym for ‘load’, according to the Pickaxe book.
Regards,
Brian.
···
On Fri, Mar 21, 2003 at 07:06:44AM +0900, feno7@gmx.de wrote:
Hello Dear Ruby-Users,
there is something confusing about the methods .dump, .load and .restore
within the Marshalling-Routines:
The Documentations says that with .dump a class could be stored on disk and
with .load it could be used as .new to create an object, but this is not
correct, only with the .restore method a new object could be created.
I tested this with ruby version 1.6.8 and 1.8.0 both same results.