Xref: utzoo comp.software-eng:4081 comp.unix.questions:24938
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!sun-barr!apple!portal!atari!imagen!sun!ichthous!mcgrew
From: mcgrew@ichthous.Sun.COM (Darin McGrew)
Newsgroups: comp.software-eng,comp.unix.questions
Subject: Re: Help on tools like SCCS, SPRs etc..
Message-ID: <141140@sun.Eng.Sun.COM>
Date: 22 Aug 90 17:32:50 GMT
References: <1990Aug16.144833.983@hjuxa> <1990Aug21.190746@Pkg.Mcc.COM>
Sender: news@sun.Eng.Sun.COM
Distribution: usa
Organization: Sun Microsystems, Mt. View, Ca.
Lines: 30

steve@Pkg.Mcc.COM (Steve Madere) writes:
>
>By the way, my copy of the RCS doc was apparrently stored under RCS and
>because everywhere where they try to describe an RCS expansion macro
>(last modification date etc.) what shows up in the doc is not the macro
>but its expansion! I quote:
>
>To obtain such identification place the marker
>	$Header: /usr/src/local/bin/rcs/dist/RCS/rcs.ms,v 1.1 89/10/30 15:54:06
>trinkle Exp $

Sigh.  Sounds like someone didn't know how to imbed a null
character into the macro to prevent it's expansion.

>Does anybody know where I can find a list of the unexpanded macros?

The unexpanded macro is just the expanded macro without the stuff
from the ':' (inclusive) to the '$' (exclusive).  In other words,
the unexpanded macro for "$Header: ...$" is "$Header$".

This is one of the advantages RCS has over SCCS--the ID strings
don't have a special "unexpanded form", so you can't clobber them
by modifying a file, and then going through the checkout/checkin
procedure and replacing the checked-out version with your
modified version.  Of course, the flip side is that there is no
way to preserve existing ID strings other than changing them (eg,
change "$Header: ...$" to "$Old-Header: ...$" in every file).

Darin McGrew			mcgrew@Eng.Sun.COM
Affiliation stated for identification purposes only.