> >... version stamp your source code in a way that can be saved into
the
> > object code
>
> Where do you put it, what do you put there?
> What platform(s) have you done this on? I know we dig into the
unix-level directories > for their date ... (PRC checks that the object
is newer than the source or it won't > > > deliver (either/both)... and
we have script/proc/macros/programs whatever that can > > > search and
display those dates from unix) ... but I'm interested in where you went
with > this. I think it's a good idea.
>
> Susan
RCS & SCCS have "keywords" that are sort of like variables that will be
replaced with the proper text. So a source block in a program header
like:
* $RCSFfile$
* $Revision$
* $Date$
gets expanded upon extraction from the rcs library (via co) into:
* $RCSfile MYPGM $
* $Revision 3.2.1 $
* $Date 2005/04/13 $
So if you put an assignment, for example, at the bottom of your program,
after the return or stop, so it would never actually even be executed:
RCS.INFO = "$Header$"
that string would be expanded in the source to
RCS.INFO = $Header: /proj/arc/CDS.BP/MYPGM, v 3.2.1 2005/04/13 cds
Exp $"
& then end up embedded in the object file, where it could be searched
for on demand.
There are several other RCS keywords.
SCCS uses "%" instead of "$" in their keywords.
cds
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
