home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!utcsri!torn!spool.mu.edu!yale.edu!ira.uka.de!math.fu-berlin.de!umn.edu!csus.edu!netcom.com!netcomsv!terapin!paulk
- From: paulk@terapin.com (Paul Kienitz)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Version Strings...
- References: <1993Jan10.173352.22592@fy.chalmers.se>
- Message-ID: <paulk.36pk@terapin.com>
- Date: 11 Jan 93 22:52:30 PST
- Organization: BBS
- Lines: 15
-
- > > Please make sure that the version string is near the beginning of
- > > the executable, so that the version command can quickly find it.
- > > This can normally be achieved by placing the code above (or
- > > similar code) at the top of one of the programs modules, and then
- > > making that module the first one in the link command.
-
- > That won't work if you use the (equivalent of SAS's blink)
- > SMALLDATA option, since that merges all the data segments.
-
- What I did with Aztec was make a separate tiny source file containing
- the version string and a coupla other revision-sensitive little
- items, and tell the compiler, for that one source file, to put all
- strings in the code segment instead of the data segment. This does
- mean that if you refer to any of those items elsewhere you have to
- use a far reference.
-