[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [PATCH] Issue 1628

From: <kfogel_at_collab.net>
Date: 2005-07-26 20:24:22 CEST

"Valik" <vampirevalik@hotmail.com> writes:
> This isn't the stone-age anymore. I find it absurd (As I've stated many
> times in this thread) that in 2005, we're having this conversation. Write
> a script/program or find one that cleans up source code formatting (I
> don't know any off the top of my head, I'm afraid). Stop the problem on
> your end; don't try to push it out to the users who more than likely don't
> care about the project's hang-ups on stylistic issues. I think a nice
> Python or Perl script doing some regular expression search/replace work on
> a file would stop style issues dead. I think there are even version
> control software out there that could run such a script in a thing called
> a pre-commit hook. Wouldn't it be nice if you knew where you could find
> VCS like that?

This suggestion keeps coming up.

Even just specifying the problem is exceedingly complex, and I am
pretty sure that writing a tool (or configuring an existing tool) to
take care of even a majority of the stylistic nits that typically come
up here would be impossible. I'd love to be proved wrong, but in five
years no one has written such a tool, and it's not because we wouldn't
like one, nor because the problem has received no attention. So while
I appreciate the suggestion, I think it's pretty much hand-waving.
This problem is Hard.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 26 21:19:33 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.