in reply to Perl 80 Chars perl line Rule
I wouldn’t hold fast to any sort of “rule,” which definitely to me smacks of the days in which we all used CRTs. Especially not at the risk of unnecessarily disturbing [large blocks of ...] source-lines that presently work, and of also seriously damaging the revision-tracking capability of the source code control system (SCCS). If, on a case-by-case basis, it appears that a block of code is inconsistent with its neighbors and therefore genuinely hard-to-read, then I would highlight that block of code and tidy it ... checking in the results (having made no other changes) immediately back into the SCCS, with an appropriate notation, “tidied this.” (I strongly advocate keeping all such commits separate: don’t change code and tidy it in the same commit.)
P.S.: I’m also not suggesting here that longer source-lines are somehow better. In fact, “you young turks” should bear in mind that one day your optometrist is going to screw-up your glasses prescription, even to the point of getting the damm things so badly cut that the top half has a different focal-length than the bottom half ... bah!
Re: Perl 80 Chars perl line Rule
Replies are listed 'Best First'.
|Re^2: Perl 80 Chars perl line Rule|
by BillKSmith (Curate) on Dec 04, 2012 at 21:49 UTC