Sorry @peter && Chris, but if you worked for me . . .
I had a standing rule in my shop. If the code extends beyond column 80, then you need to break the line., or re-code the expression for clarity. With the exception of a large case statement, any logical block of code that exceeds a single screen of 25 lines should be broken up into smaller functions/sub-routines. This is simply good programming practice for writing maintainable code.
I'm a boolean algebra guru. If I *ever* see an if with an expression that is 256 columns wide, or if I have to think more than 2 seconds on what it says then some programming type is about to get a new *ssh*le.
While one may *read* left to write, one will follow steps top to bottom. Programs are STEPS of instructions, top to start bottom to finish, and each thought should be concise and to the point one step down at a time. The problem is all you kids graduate from college where you've been writing code in a vacuum, and you've never had to actually go back and read some of the sh*t some other PFY wrote 2 years ago and fix something. I can assure you you will not have any trouble following *any* of my code.
And I'm probably going to slug the next little pr*ck that writes something like:
if ( 6 < day_of_week && 20 < hour || 8 > hour and 1 > day_of_week)
again. . .
Very cute, but you made me STOP and THINK about what you were trying to say. If *I* had to stop and think, some other poor slob is going to get lost and mis-interpet the expression
Widescreen is wonderful for accountants with spreadsheets, but if you are writing code off the right hand edge of the screen then you are inately writing code that is extremely difficult to follow. Quit writing essays, and start writing code.
My .02 (tupence?)