|
I use Consolas too, it's really good for VS and other fixed-width apps...you should try it.
|
|
|
|
|
To many artifacts an low resolutions.
We are a big screwed up dysfunctional psychotic happy family - some more screwed up, others more happy, but everybody's psychotic joint venture definition of CP
Tree<t> in C# || Fold With Us! || sighist
|
|
|
|
|
|
|
I use Bitstream Vera Sans Mono everywhere when a fixed size font is required, and Bitstream Vera Sans for the rest. Looks great with font size 8.
|
|
|
|
|
|
|
Free "Pronfont" by Tobias Jung is very readable at small point size. Even 7 pts text is still recognizable, 9 pts is easy to the eyes.
Profont home
|
|
|
|
|
I've worked on code bases where class names were wider than 80 char's.
I think its usefull if you're developing on an IDE like vi or emacs. I think with an auto completion feature, I'd rather have wider source code that makes sense to read, rather than have a line of code that wraps around 12 lines because of cryptic naming conventions.
|
|
|
|
|
Class names longer than 80 characters? Run away! Run away!
David Veeneman
www.veeneman.com
|
|
|
|
|
I had to create dev training material on it too, try pasting a class like:
AclassWithReallyLongNamesThatDidThisAndThatAndAnotherBecauseWeLikeToWriteLongClassNamesClassAndCouldntImagineNamingThingsShorterBecauseNobodyWouldBeAbleToUnderStandWhatItDid
that was implemented as a singleton with a similarly long instance property and service method that was about as long, into word in a blockquoted box and still make it look good (the font was so small that it wasnt even readable on the final print media.
They actually ran into a bug that was caused by reflection not being able to load a type because its name was longer than 256 characters.
|
|
|
|
|
That's worth a five on the original message!
BTW, you're web site is pretty cool--I've bookmarked it.
David Veeneman
www.veeneman.com
|
|
|
|
|
wow, hey thanks on both accounts.
|
|
|
|
|
I try to stay under 80, but at times I'll go out a bit farther to avoid
Long API names like GetProcAddress("DwmEnableBlurBehindWindow") also break the 80-column barrier.
--Mike--
Visual C++ MVP
LINKS~! Ericahist | PimpFish | CP SearchBar v3.0 | C++ Forum FAQ
|
|
|
|
|
I'm mostly the same way, except it's ~100 chars I usually try and stick to. But, that's mainly because of my monitor/resolution. I'd up it if I had the screen space.
Jeremy Falcon
|
|
|
|
|
Yeah, I usually type until the caret is at the right border of the screen (that is about 120 chars) .
Don't try it, just do it!
|
|
|
|
|
Me too. I find it helpful to be able to view 2 files vertically tiled on a 1600x1200 display.
/ravi
|
|
|
|
|
Michael Dunn wrote: DwmEnableBlurBehindWindow
Are we expecting a Windows Vista article?
|
|
|
|
|
|
I developed the habit of trying to keep it under 80 characters, years ago. I might actually want to do a printout sometime, using a font size I can read. Lately I have been programming in VB.NET and the generated code does not care how many characters there are per line, so I am going with the flow.
INTP
"Program testing can be used to show the presence of bugs, but never to show their absence."Edsger Dijkstra
|
|
|
|
|
I mostly press Enter in column 81 (Even with comments),
So I selected 2nd choice, however first one (80) is much simillar but it says 80 or less.
//This is not a signature
while (I'm_alive) {
printf("I Love Programming");
}
|
|
|
|
|
Nuff said
Depends on IDE and monitor since my code very rarely viewed by anyone else except myself.
Formula 1 - Short for "F1 Racing" - named after the standard "help" key in Windows, it's a sport where participants desperately search through software help files trying to find actual documentation. It's tedious and somewhat cruel, most matches ending in a draw as no participant is able to find anything helpful. - Shog9
Ed
|
|
|
|
|
Another choice for Depends is
- The font of your code
|
|
|
|
|
Most code is 80 or less. But, occasionally I will tack a
comment on the end that stretches the entire line much longer.
I like to be able to read my code without scrolling (horizontally).
But, I don't mind if the comments are more extreme. AND -- I don't
spread out to often.
WedgeSoft
|
|
|
|
|
It's the other way around for me. Comments are strictly 80, but sometimes the code goes wider because it's easier to read. This is typical of code where you need to make.a.lot.of.object.derefences.with.long.member.names(with,lots,of,needless,parameters), such as in .NET and Win32 API calls.
I know better than to design my own structures like that.
---
Shawn Poulson
spoulson@explodingcoder.com
|
|
|
|