Brace style
-
I'm even more anal about bracing. I use if(blah) { stuff even if only one line. Notice the indent; } That way I can line up the if, else etc and eyeball for closing braces to see which block the code is in. I find: if(blah) { dgf dfd df df fdf dfdf } else { dfd df df dsf dg } method annoying. You are forced to look at the first character of each line to see if it is the brace your looking for, rather than scan down the column where the brace your looking for should be.
-
Oh crap, I got slaughtered by white space removal. The buggers ;) Corrected
if(blah) { stuff even if one line. Notice the indent. } -
This is interesting, I myself used the latter, but in the programming course Ive done they teach using the former, although Ive gotten used to programming like that i still dont like it and prefer having the extra line breaks
-
Which one you prefer ?
if{
//do something
}Or
if
{
//do something
}
printf("Navaneeth!!") www.w3hearts.com
Prefer? My preference is irrelevant. The ancients said it best.. when in Rome, do as the Romans. When in someone else's code, match their style. Unless you're writing C#, in which case, Caesar Gates's cronies have decreed how we will all do our braces, spacing and indentation. Fine, whatever, we've all got more important things to do than to fight it anyway.. right? After 20 or so years of reading all different brace styles, you'll pretty much cease to see them anyway.. as long as it is consistent throughout a file. Remember, Rome-Romans. What should you do in completely new files? Sure, fine, whatever. Which do I do in new files? The second one. Why? Because I was asked to. Why was I asked to? I dunno, probably because someone had a harder time of understanding the code with the first one. Why do I bother to comply? Because they claim it helps them.
patbob
-
Which one you prefer ?
if{
//do something
}Or
if
{
//do something
}
printf("Navaneeth!!") www.w3hearts.com
How about letting the development environment decide based on who you are... that way if you like it one way and your colleague likes it formatted another way, you both can have your cake and eat it too.
-
I don't like extra line breaks. I've been reading code for many years and I don't need the visual noise. I like things in a smaller space. I leave out braces for single-statement blocks, and I love the (x ? y : z) notation. It's a non-issue though, because VS can quickly re-format code to your personal style. It takes a bit of fiddling with the options, but you can get whatever you want out of it.
"Quality Software since 1983!"
http://www.smoothjazzy.com/ - see the "Programming" section for freeware tools and articles. -
Which one you prefer ?
if{
//do something
}Or
if
{
//do something
}
printf("Navaneeth!!") www.w3hearts.com
-
My favourite (probably) apocryphal story on this point is that K&R used their style for no other reason that to save space (and thus publishing costs) in their book. I sooo want this to be true. What about this one: if (something) { do_something(); } While we're at it... Tabs or spaces? :-)
-
The latter. The former is used only by miscreants and rogues. :suss:
----
i hope you are feeling sleepy for people not calling you by the same.
--BarnaKol on abusive words
-
Which one you prefer ?
if{
//do something
}Or
if
{
//do something
}
printf("Navaneeth!!") www.w3hearts.com
If you have an ounce of artistry in your soul as a programmer you would use the latter. The first one drives me nuts, it just screams out to me to be dropped down to the latter style. I find the visual style and symmetry of code to be equally important as comments in understanding it and life is to short to play "match the braces" when editing existing code. Every block of code should be indented from it's surrounding block and the opening and closing characters should be on the same column.
"110%" - it's the new 70%
-
Thats crazy, even marking it as code this site doesn't keep your formating. Whoever coded this webform is going to go to scripting hell. Every thing he codes will be parsed and emulated on a Comandor 64, no native code for you:laugh:
The pre tag is what you want. code is only intended for a small snippet of code in the middle of plain text. Yes it is confusing. :mad:
-- You have to explain to them [VB coders] what you mean by "typed". their first response is likely to be something like, "Of course my code is typed. Do you think i magically project it onto the screen with the power of my mind?" --- John Simmons / outlaw programmer
-
The pre tag is what you want. code is only intended for a small snippet of code in the middle of plain text. Yes it is confusing. :mad:
-- You have to explain to them [VB coders] what you mean by "typed". their first response is likely to be something like, "Of course my code is typed. Do you think i magically project it onto the screen with the power of my mind?" --- John Simmons / outlaw programmer
-
Which one you prefer ?
if{
//do something
}Or
if
{
//do something
}
printf("Navaneeth!!") www.w3hearts.com
if (condition) then do something endif -CB :)
-
As far as "proper" I sorta meant it as a tongue in cheek remark. The style to which one uses brace formatting is really up to the user. It has its merits either way.
All things being equal, tommorrow will never equal today
I prefer the former, but VS 2005 forces me to use the latter. Everyone in my company uses VS 2005 so I have to use the same style to be consistent. Jim
-
Which one you prefer ?
if{
//do something
}Or
if
{
//do something
}
printf("Navaneeth!!") www.w3hearts.com
-
Last one complies to coding standards. First one is for folk who don't know any better. How about an if that runs only 1 line of code. A:
if{//do something} dothis other code.....B:if{//do something} { dothis } other code.....Grady Booch: I told Google to their face...what you need is some serious adult supervision. (2007 Turing lecture) http://www.frankkerrigan.com/[^]
Frank Kerrigan wrote:
Last one complies to coding standards
And if the coding standard said to jump off a bridge?
-
Which one you prefer ?
if{
//do something
}Or
if
{
//do something
}
printf("Navaneeth!!") www.w3hearts.com
All paired items (braces, brackets, parentheses, quotes, and "angle-brackets") (and commas within a list) should be aligned either horizontally or vertically.
-
The latter. The former is used only by miscreants and rogues. :suss:
----
i hope you are feeling sleepy for people not calling you by the same.
--BarnaKol on abusive words
-
Which one you prefer ?
if{
//do something
}Or
if
{
//do something
}
printf("Navaneeth!!") www.w3hearts.com
I have a scientific(ish) test for this. * Print out a sample of code on A4 paper in 10 point courier font. * Stick it to the wall * Stand several metres away (more if you have good eyesight) * If you can still clearly discern the structure of the code then you have a good layout style
-
Which one you prefer ?
if{
//do something
}Or
if
{
//do something
}
printf("Navaneeth!!") www.w3hearts.com
Well, it depends on the context, code, tool used, etc... Sometimes one can be more suitable than the other. For example, when functions are larger than a page, if you position in the closing brace, (X)Emacs helps you and prints in the minibuffer the matched opening brace. If you use the former (e.g.: if (x == 0) { ) it is helpful. I'm sure you can find pros and cons for both. Just my 2 cents, Tomas