> If anybody does go through with implementing this stuff, branch "functions"
> (I believe somebody else already mentioned this in passing) seem to make more
> sense to me than more magic tags.
I think this was me.
> Rather than a bunch of new magic tags, excepting perhaps '.trunk', allow
> magic functions such as, '.parent', '.tail', and '.head' to be appended to
> branch tags. Allow multiple concatenations, of course, for constructs like,
> 'current_branch.parent.parent.tail' and 'current_branch.parent.head' and
> '.trunk.head'. Also, assume an empty tag is the current branch ( '.parent'
> would be equivalent to 'current_branch.parent').
The postfix property like ".parent", etc., works for most.
You may want to have the binary most_recent_common_ancestor(rev1,rev2),
however, which may motivate multiadic function notation in addition
to postfix notation.
> It seems to me that this would be almost as simple to implement as that list
> of magic tags if you were inclined to do such - I think the lookup simply
> becomes recursive somewhere, and adds the most extensible functionality.
I actually had code for these, but only my -r. code made it into
RCS 5.6 (as -r$, I believe - deduce version from checked
out files).
Don't ask me to dig it up - it's long gone, on a company server
far, far, away.
