Re: How to get log messages *after* one tag up to another tag

[Larry Jones]

Doyle, Jim writes:
> 
> Would this really complicate the code, though?  I haven't looked at the
> source much, but I have seen that there seem to be functions for getting the
> origin of a branch ("RCS_getbranch"? or "RCS_whatbranch"?).  As long as you
> can jump from a branch revision to the branch origin, and get from a
> revision to the
> one that precedes it within a branch, it looks like listing the revisions
> wouldn't be too bad.  

I don't know as it complicates the code, but it certainly changes it. 
The existing code doesn't really care about branch origins,  it just
goes through the list of revisions and for each one asks, "Is this
revision greater than the start of the range and less than the end of
the range?" and, if so, includes it in the output.  The catch is that
the primitive that compares two revision numbers requires that both
ranges have the same number of dots and thus can only return "less
than", "equal", or "greater than".  In the more general case, it needs
to be able to return "unordered" as well, and all the callers need to be
able to deal with that new return value.

-Larry Jones

That gives me a FABULOUS idea. -- Calvin