read and write glyphs

Article View: comp.windows.interviews

Article #506

Back to comp.windows.interviews Previous Next

#506

From: Michael Hines
Date: Tue, 18 Aug 1992 19:09

9 lines
889 bytes

I am curious why read(&istream) and write(&ostream) didn't make it into the
glyph protocol. Was it because the requirements of applications for
saving and restoring state too diverse?
I know Unidraw has the concept of a catalog with each
object being able to return its type (so one knows what constructor to
call when reading it back in). Is it possible/convenient to make use
of that mechanism without mixing 2.6 and 3.1. Or should we not be concerned
with extensive mixing?

Technical Details

Message-ID: <4651@news.duke.edu>

Path:

arc1-ca.pugleaf.net!sparky!uunet!europa.asd.contel.com!darwin.sura.net!jvnc.net!rutgers!concert!duke!news.duke.edu!neuro.duke.edu!hines

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!sparky!uunet!europa.asd.contel.com!darwin.sura.net!jvnc.net!rutgers!concert!duke!news.duke.edu!neuro.duke.edu!hines
From: hines@neuro.duke.edu (Michael Hines)
Newsgroups: comp.windows.interviews
Subject: read and write glyphs
Message-ID: <4651@news.duke.edu>
Date: 18 Aug 92 19:09:00 GMT
Sender: news@news.duke.edu
Distribution: usa
Lines: 9
Nntp-Posting-Host: timshel.neuro.duke.edu