I hereby dedicate this thread to stupid coding standards from stupid programming style guides. I'll start.
>> Limit line lengths to 80 characters. There are still many devices around that are limited to 80 character lines; plus, limiting windows to 80 characters makes it possible to have several windows side-by-side. The default wrapping on such devices disrupts the visual structure of the code, making it more difficult to understand.
NO. It's 2009 for fuck's sake, no one is programming through telnet on a goddamn serial modem in DOS. If your editor is fucking up wrapping, FIX IT, or get a better one. Limiting line lengths because of *default* options on editors? Who the fuck is programming that can't configure their goddamn editor?
Actually, there seem to be some few really strange people that are "programming through telnet on a goddamn serial modem".
It's also easier to read lines that don't scroll way too far off. I'm guilty of not following line length "standards" myself, and I'm sometimes bitten by way too long lines. It may be better if I did follow such rules.
Name:
Anonymous2009-11-01 14:30
The point about having more than one window side-by-side is fair, but we still have to get with the times. These days, virtually all programmers have at least 1600×1200 screen resolution, 2 monitors, and use a 9–10pt font. This allows for at least 100–120 characters per line, with plenty of room left over for a second window.
>>3
I think 1600x1200 is a bit optimistic. Some of us are poor, you know. I have a 3-year-old LCD and it doesn't support said resolution. Though I do have two monitors of differing aspect ratios.
I'm not aware of anyone that keeps their editor of choice maximized, however. The synergy of having Google/any number of reference websites and your editor open at once is too great to ignore.
That said, I do disagree that 80 characters per line is the be-all and end-all of standards. Lines that long should be refactored. Long if statements though are sometimes impossible to beautifully refactor. Then again, long if statements don't just disappear with 80 characters per line either. So I don't know.
>>10
1280x768 will still get you 160 columns and 48 rows of (rather big) 8x16 font, and if you use something like Proggy (6x13/7x14) that's 200+ columns and 50+ rows. These days 1024x768 is the minimum, and you can still get 170+ columns of 6-pixel-wide font on that. Unless you're using 640x480 for some reason, the 80 column limit is obsolete.
Name:
Anonymous2009-11-02 13:18
80 columns is still something to strive for, but I'd say 100 columns is acceptable. I'd say that keeping comments within 80 columns is still a good idea to promote readability.
Name:
Anonymous2009-11-02 14:51
I use three widescreen 24" displays. Fuck poor programmers, they should go back to India or something.
Name:
Anonymous2009-11-02 15:08
YEAH FUCK YOU POOR PROGRAMMER FUCKS
WHY DONT YOU JUST GO BACK TO INDIA OR SOME SHIT
FUCKERS
Name:
Anonymous2009-11-08 9:16
Short lines are a better option.
Name:
Anonymous2009-11-08 9:39
i have 1600x1200, but personally find lines longer than 100 columns difficult to read.
Name:
Anonymous2009-11-08 9:39
>>15
You'
re
stu-
pid
the-
re
is
no
adv-
ant-
age
to
the-
m.
Name:
Anonymous2009-11-08 10:00
S
h
o
r
t
l
i
n
e
s
a
r
e
f
i
n
e
t
o
o
Name:
Anonymous2009-11-08 10:07
w47
w4t
wat
Name:
dasuraga!8GgBtN/zr.2009-11-08 10:17
I program in text editors with 12-14 point fonts.... so the 80-column standard is useful for me. With long if statements I just use the magic of multi-line statements(if you're writing things that long, there's something wrong with your logic in most cases)
Name:
Anonymous2009-11-08 10:38
>>20
Maybe you should fix you're eyesight instead of expecting the world to cater to cripples.
Name:
Anonymous2009-11-08 10:47
>>20
If you follow the "80-column limit" and "at most one statement per line" limit and you're still too wide then line continuations are perfectly sound.
For example:
Object * pointless(int a, double b, const std::string &c)
{
ObjectFactory *factory = new ConcreteFactory;
Object *ptr = factory->create(a, b,
aNameWhichWontFitInThePreviousLine(c));
return ptr;
}
But there's a problem with this approach. I'll give you a chance to guess.
Answer: You're using SEPPLES.