Xref: utzoo comp.sys.att:5353 comp.unix.wizards:14372
Path: utzoo!yunexus!geac!geaclib!daveb
From: daveb@geaclib.UUCP (David Collier-Brown)
Newsgroups: comp.sys.att,comp.unix.wizards
Subject: Re: Looking for "undump" for SysV
Message-ID: <3611@geaclib.UUCP>
Date: 28 Jan 89 02:45:12 GMT
Article-I.D.: geaclib.3611
References: <1527@sauron.Columbia.NCR.COM>
Organization: GEAC Computers, Toronto, CANADA
Lines: 26


> In article <404@cwjcc.CWRU.Edu> ferencz@cwsys3.cwru.Edu (Don Ferencz) writes:
>> I have been looking (high and low) for a UNIX SysV.3 version of
>> undump (or an equivalent a.out <-> core combining program).
 
From article <1527@sauron.Columbia.NCR.COM>, by wescott@sauron.Columbia.NCR.COM (Mike Wescott):
> As one poster suggested, it may not be that much of an advantage for TeX.

  And in general, you want a facility to store configuration
information in an easy-to-access manner. Dump/undump and unexec are
two well-known ways of doing this, but there are others.  One I like
is to write a (necessarily non-portable) binary file from the
contents of a struct, having created it with a #ifdef'd version of
the standard source.
  This doesn't really work for TeX, though, as you'd have to write a
**remarkably** large chunk of core (;-)).
  Or, if you don't like non-portable tricks, have the configuration
compiled to a user-specific library and dynamically links it by name
(this assumes that you have dynamic linking, of course).

--adev
-- 
 David Collier-Brown.  | yunexus!lethe!dave
 Interleaf Canada Inc. |
 1550 Enterprise Rd.   | He's so smart he's dumb.
 Mississauga, Ontario  |       --Joyce C-B