It's possibly true, and looking at a random example of a bit of my code I could actually fix most of the long lines simply by splitting them in two without much loss of readability, and I have used subroutines in some places so none of the long lines are caused by indenting off into oblivion.
I've got some rather horridly long regexps that I'm not sure I could make shorter though. (Although actually I can spot a way to lose about 8 characters off the worst instance, *ahem*, which would at least get me under 100 characters). Someone better at regexps than me might well be able to improve it though.
And some print statements where I'm printing a c. 80 character line of output and it seems daft to create a variable to put it in just to make the code narrower, when no-one who's going to be reading this code is likely to be doing it restricted to 80 cols, those are only about 90 cols.
My worst lines seem to be 123 cols, including a comment on the end of the line. And I think those are getting a bit too long. I shall do better in future.
Basically a 100 column emacs window is just a nice size though :)
no subject
I've got some rather horridly long regexps that I'm not sure I could make shorter though. (Although actually I can spot a way to lose about 8 characters off the worst instance, *ahem*, which would at least get me under 100 characters). Someone better at regexps than me might well be able to improve it though.
And some print statements where I'm printing a c. 80 character line of output and it seems daft to create a variable to put it in just to make the code narrower, when no-one who's going to be reading this code is likely to be doing it restricted to 80 cols, those are only about 90 cols.
My worst lines seem to be 123 cols, including a comment on the end of the line. And I think those are getting a bit too long. I shall do better in future.
Basically a 100 column emacs window is just a nice size though :)