🚀 go-pugleaf

In article <6v3uei$593$1@shell17.ba.best.com>,
	jbuck@best.com (Joe Buck) writes:
>Nick Andrew <nick@zeta.org.au> wrote:
>>It occurred to me on discussing this issue that perhaps the save format
>>(what is written to disk) may be closely related to the data structures
>>used in the program.
>
>That's correct.  Microsoft is fond of "serialize", a scheme for dumping
>an image of a C++ object hierarchy to disk.  The system is rather poorly
>designed and inflexible (there is a versioning system but it requires
>base classes to know version numbers of derived classes and other evils
>like that), but it has the small benefit of giving programmers a simple
>way to do a persistent store.
>
>>It may be that when the user "saves" a document that the in-memory data
>>structures are dumped to disk with little or no formatting, which results
>>in the oft-reported junk and deleted text in the output file.
>
>Correct.  (I'm amazed that business puts up with the information leaks
>this causes; people who publish Word documents often are publishing text
>from earlier drafts that the author thought was deleted).

I've used word6 a lot and I got suspicious about how it took so (expletive)
long to save to floppy (so much that I wrote a macro to save to HD and copy
to floppy and it was 2-5 times faster!) so I checked out the dataflow with
a cache program and saw that it wrote the same thing/read it back twice! odd!

also I think the 'quick-save' option just dumps the data structure whereas the
default is to 'defragment' the virtual file-system which makes up the word6
file...

SammyTheSnake
-- 
SammyTheSnake@HotMail.com
PHUAE@Warwick.ac.uk S.A.Penny@Warwick.ac.uk
http://www.geocities.com/Athens/Forum/3353/
Check out my (E)TLA refference page at http://www.warwick.ac.uk/~phuae/