Re: Possible way to support $Log$

Lübbe Onken wrote:

> How about embedding the log between $LogN$ and $LogEnd$ tags
> where N is the number of log entries to include. If N is omitted, all
> log entries are shown.

The reason I specifically didn't want to suggest a $startlog$ and $endlog$ pair
is because then the client code cannot immediately read all applicable bytes,
but has to read line by line looking for the closing tag. It would also
preclude the chosen closing tag from being part of the $Log$ entry itself (sans
some escaping rules). By having a single tag with a fixed/precalculated size,
the client code can immediately slurp up the applicable text (and in most cases
just ignore it, i.e. for diff purposes).

The more I look at this, the less I like even my own solution, especially given
that most of the time the $Log$ entry will be required to exist in a source file
as a comment. For those languages with block comments, it is easy; for those
which only have line comments, it requires the client to perform additional
magic to make it work. Urghh...

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org