[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Running fixcc.py
From: |
David Kastrup |
Subject: |
Re: Running fixcc.py |
Date: |
Sun, 22 Mar 2020 22:04:23 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
Dan Eble <address@hidden> writes:
> On Mar 21, 2020, at 11:26, David Kastrup <address@hidden> wrote:
>> it got a bit lost in other things, but I think I would want to run
>> fixcc.py right now, reformatting the C++ stuff (it doesn't help with the
>> conventions for template arguments but there are comparatively few of
>> those).
>
> Did you use astyle 2.04 or another version? I built 2.04 from source
Uhm, I did not actually go to that effort and just used --sloppy.
> and ran it on master and I see a handful of differences in 3 files.
3.1. I am afraid that I may have updated my system since the review,
and that looks like more of a version update than what I did the review
with. Yes, this is more along the line of --extra-sloppy . This is
sort of embarrassing, but I haven't even considered the implications of
just using what is there when a particular version has been declared
"standard" and people may actually use it in order _not_ to cause
spurious reformatting.
So where should we go from here?
--
David Kastrup
- Running fixcc.py, David Kastrup, 2020/03/21
- Re: Running fixcc.py, Torsten Hämmerle, 2020/03/21
- Re: Running fixcc.py, Dan Eble, 2020/03/21
- Re: Running fixcc.py, Dan Eble, 2020/03/22
- Re: Running fixcc.py,
David Kastrup <=
- Re: Running fixcc.py, Dan Eble, 2020/03/22
- Re: Running fixcc.py, David Kastrup, 2020/03/23
- Re: Running fixcc.py, Dan Eble, 2020/03/23
- Re: Running fixcc.py, David Kastrup, 2020/03/23
- Re: Running fixcc.py, Dan Eble, 2020/03/23