I started exceeding that notional 80-char barrier the first time I got a VT-100 (circa.'79) with its 132 wide mode.

These days my code generally stays within 132 wide, as my 21" (1920x1080) monitor allows me to have 2, 132x64 (using 10-point Consolas) tiles side-by-side, but it is in no way sacrosanct. If the structure of the code is such that it feels right to go longer, I do.

I find the justifictions for sticking rigidly to 80/72/64 completely bogus. If your terminal software won't let you use more than 80 characters, get better terminal software. If your editor doesn't allow you to configure it to not wrap at some stupid limit; get a better editor. And the whole idea of structuring code into old fashioned broadsheet newspaper columns makes no sense -- no one 'reads' code like a newspaper article or novel.

And the using the kind of de-structuring that is epitomised by the Perl sources, in order to comply with such outdated, arbitrary limits, is tantamount to a criminal act.

The tokens that make up the lines of source code are only (actually, probably less than) half the story, the structure of the code is equally, if not more important; and good -- or at least consistent -- indentation tells you more at a glance about that structure, than any amount of pouring over the code whilst looking at it through a vertical letterbox slot ever will.

Collapsing levels of indentation so as to avoid spilling over pointless line on the right of the screen, is like removing the staffs from sheet music.

At this point I want to lay into interleaving pod with code; but I better shut up :)