Re: keword (re) expansion

[Jim Hyslop]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

(I should have combined this with my previous response - sorry for the
extra message).

Russ Sherk wrote:
>> Maybe it should be expanded the same as RCS keywords.  Any reason why not?

I think the inconsistency arises because $Name$ is the only keyword that
can change value when fetching from the repository. All other keywords
for a given revision are immutable.

In order for the $Name$ keyword to be expanded each time an update is
specified, then the update test will have to be modified. If the file is
indicated as unmodified, then an additional scan for the $Name$ keyword
will have to be made (assuming the -k options are set), and if found,
force an update. Question is, how much of a performance hit would this
extra step be?

Note, by the way, that the "Sticky tag:" line in 'cvs stat' reads info
from CVS/Entries, not from the RCS keywords.

- --
Jim Hyslop
Dreampossible: Better software. Simply.     http://www.dreampossible.ca
                 Consulting * Mentoring * Training in
    C/C++ * OOD * SW Development & Practices * Version Management
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFD+AK/LdDyDwyJw+MRAvKFAKDH7oZSxwqyN+8qCLj8TErA96H71gCgrlSx
0i0pieUlrBXTvizzV189Bcs=
=Joc3
-----END PGP SIGNATURE-----