 
| Subject: | |
| From: | |
| Reply To: | [log in to unmask][log in to unmask], 16 Mar 1998 21:33:56 -0800368_- Hello Wendy, copy 3000-L: Last week Mark Bixby forwarded an interesting message from you. First Mark said: > DNS/iX is based on my port of BIND/iX 8.1.1, and if > you're going to be at IPROF98, you can see me demo > BIND/iX on Thursday 3/19 @ 8 AM. Even though I'm a semi-swing-shifter, I plan to get up for it.... :-) [...]48_16Mar199821:33: [log in to unmask] |
| Date: | Mon, 16 Mar 1998 10:45:53 PST8 |
| Content-Type: | text/plain |
| Parts/Attachments: |
|
|
Since I also 'contributed' to this chatter about '$VERSION ...' and how to
user 'version.pub.sys' to report the version strings, I'll report what I've
found out and perhaps suggest a method for automatically including
'$VERSION' information.
Almost all of the HP compiler commands, nowadays, are invoked using command
files. So one can make changes to 'COB85XL', 'COB85XLK' and 'COB85XLG' or
the corresponding files for the other compilers, remembering to reapply the
changes after each OS upgrade, to automatically include '$VERSION'
information. Below you'll find an example of the changes that I performed
for out site (The upshifted line is the 'added' command):
....
setvar _cob_parm _cob_parm+$01
file cobtext=!text
SETVAR _COB_INFO _COB_INFO + "$VERSION '" + FINFO("!TEXT","FULLFNAME") &
+ " !HPDATEF !HPTIMEF'"
endif
if "!list" <> "" then
....
An example of using the above against a main module and a subroutine called
out of said main as well as using 'version.pub.sys' against the resulting
native mode program follows:
:cob85xl cob,rlx
:cob85xl cob1,rlx
:link rlx,ccob
:version ccob
VERSION C.50.03 Copyright (C) Hewlett-Packard 1987. All Rights Reserved.
CCOB.SUPUTIL.SYS
SOM #1
$Header: nrt0.s,v 1.12 87/06/08 09:36:52 cary Exp $
COB.SUPUTIL.SYS MON, MAR 16, 1998 9:31 AM
COB1.SUPUTIL.SYS MON, MAR 16, 1998 9:32 AM
MAX STACK SIZE: 393216
MAX HEAP SIZE: 81920000
CAPABILITIES: BA,IA
UNSAT PROC NAME:
ENTRY NAME:
LIBRARY SEARCH LIST:
One area that this may not work properly is when the compilation is
initiated directly from the editor. Some editors set up the needed
parameters for the compiler and 'bypass' the command file.
|
|
|
