On 2010-11-05, Grant Edwards <[email protected]> wrote:
> On 2010-11-05, Tim Harig <[email protected]> wrote:
>> On 2010-11-05, Steven D'Aprano <[email protected]> wrote:
>>> On Thu, 04 Nov 2010 21:47:59 +0000, Tim Harig wrote:
>>>
>>>> I have seen huge patches caused by nothing more then some edit that
>>>> accidently added a trailing space to a large number of lines. White
>>>> space mangling happens all the time without people even knowing about
>>>> it.
>
> And how does that affect a Python program? The same as it does a C
> program.
I wasn't making any statement of C versus Python in this thread. Those
have been covered elsewhere. I was responding to your assertion:
It exists because so many people change whitespace intentionally
in C source code because no two C programmers seem able to agree
on how to format code. Diff -b allows you to attempt to ignore
semantically null stylistic changes made by programmers.
That is clearly wrong. If a C programmer changes the format of the code,
it is almost universally true that they will make changes that affect more
then just the whitespace on a single line. Diff will register these
changes even with the -b option. I provided a couple of common scenerios
that are more likely to have justified the -b option.
--
http://mail.python.org/mailman/listinfo/python-list
