Billy Tanksley <btanksley@hifn.com> writes:
> Perhaps that's the answer -- make line ending handling into an 'external'
> feature (i.e. one which uses the extension API), which just happens to be
> shipped with Subversion. It can be an example of how to use that API, so if
> someone wants to build that C++ reformatter, they can use the line ending
> formatter as a starting point.
As someone who once suggested that there be a way to format/deformat
source code on checkin/checkout and was told that the repository
shouldn't ever munge the data, count me in as someone who finds it
strange that line endings are for some reason exempted. As I
suggested once before, I think that making line ending conversion and
keyword expansion "external" features makes the most sense to me. It
also solves the problem mentioned earlier about people asking for
$NetBSD$ and $Id$ keywords. If they're not hard coded parts of the
application but rather an easily modified extension, people can
implement what they want without obscure hacks or having to fork the
source.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:52 2006