On 06/02/2012 11:51 AM, Jacques Le Roux wrote:
Hi Adam,
I don't know what others think about that, but personnally I don't like
it. For instance we get now from beginning of the line
(trailers blanks included)
The terminal on my laptop is 198 chars. At work it's 147. But that
doesn't matter.
I only combined lines that were affected by the deprecation that I've
been doing. I didn't do it to all files.
Also, in several of those files, they were not self-consistent. Some
times, even in the same method, and in the same general area of the
method, some lines were split, and some were all on a single line. And
the split wasn't consistent.
There is no way that we can ever enforce a single, unified width.
Screen sizes change, font sizes change. It's too political to come up
with a solution.
So, the only fallback is to never split. Then it is up to each
end-developer to modify their display to handle the long lines.
ps: This is similiar to svn storing files in the repo with one kind of
line-ending, then upon checkout(or when checking-in), it converts
automatically.
ppd: This is also similiar to keyword expansion; it happens at checkout
time, but the repo stores it unmodified.
