Subject: Re: [boost] coding conventions
From: OvermindDL1 (overminddl1_at_[hidden])
Date: 2010-01-06 05:44:19
On Wed, Jan 6, 2010 at 2:59 AM, Christopher Jefferson
> On 6 Jan 2010, at 00:52, OvermindDL1 wrote:
>> There are things we can run on the source that reformats it all to
>> proper guidelines, including setting tabs, moving braces where
>> necessary, so forth, could always use one of those over the entire
>> Boost library.
> The biggest problem with such tools is that they break diffing, so they would break the connection between release and trunk, between version before and after the reformat, and also break any patches any users keep (I myself keep a few patches on my local version which usually apply without problem to the next version, but I'm sure wouldn't apply after such a reformat).
> I would also be shocked if any such tool worked well on the complex C++ code stored in boost. I have not been a tool which formats my own C++ code well, as most tools work by simple regexps, whereas C++ requires much more context.
Perhaps one can be made using Clang? Its C++ analysis is near
complete (its code generator is still being worked on though), so it
might be a good side project, hmm, ideas...
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk