Where do you put the braces?

[Robert Little]

I line the braces up such as in: class Cat { //blah }; It is much easier for me to follow. The other thing I do is get a good code editor and customize the "Beautify Source" option to my liking. I then run that and it usually barfs if I have a missing brace. Which is too often. Another thing I always do is use braces for my if statements and loops. Even if it is a simple if statement that does not require braces I use them. It makes it so much easier when I have to return to the code to figure out exactly what I was trying to put into that if statement.

[Paul M Watt]

The primary reason that you see code written like this in books is to save page space: void foo { // stuff }

---

Build a man a fire, and he will be warm for a day
Light a man on fire, and he will be warm for the rest of his life!

[Link2600]

Do you mean you use line up method too? Do you do the following too? class Cat { // codes };

[Paul M Watt]

Yes, I code like this: class Cat { // codes }; I liberally use newlines and I like to organize my braces vertically. I have seen a variety of ways that people organize their code, especially when it comes to the use of braces. I think the bottom line is what is most readable to you and your team of developers that you work with.

---

Build a man a fire, and he will be warm for a day
Light a man on fire, and he will be warm for the rest of his life!

[Shafiee]

If it's correct, you may want to declare a class like: Class Cat { Cat(); ~Cat(); //some other code}; I don't think only saving page space is assumed!

[Lost User]

I always do it the first way. It takes up a few more lines, but the matching pairs are much easier to see, much neater. Elaine :rose: The tigress is here :-D

[markkuk]

The One True Way to put the braces is the one used by Kernighan&Ritchie, and all other styles are heretic abominations. ;P

[Anonymous]

I do as : class Cat { // codes }; I think this form is better.

[Michael Dunn]

For further reading: Braces and brackets[^] --Mike-- Latest blog entry: *drool* (Alyson) [May 10] Ericahist | Homepage | RightClick-Encrypt | 1ClickPicGrabber "You have Erica on the brain" - Jon Sagara to me

[John M Drescher]

I have seen many discussions about this subject on this site. You may try a search to see if you can find them. Anyways, I use the first method for classes annd functions but the second for just about everything else. To me it is a matter of saving space. John

[Michael P Butler]

markkuk wrote: The One True Way to put the braces is the one used by Kernighan&Ritchie, and all other styles are heretic abominations. :-D that's fine for C code but C++ does it properly Michael 'War is at best barbarism...Its glory is all moonshine. It is only those who have neither fired a shot nor heard the shrieks and groans of the wounded who cry aloud for blood, more vengeance, more desolation. War is hell.' - General William Sherman, 1879

[ZoogieZork]

I've used both styles, read code using both styles, debugged code using both styles, and as far as I'm concerned, I have no problem with either form. It's not really brace matching I have problems with -- it's parens (I once spent almost a day trying to debug a parser written in Scheme that boiled down to a missing end paren... paren matching? What's that?) :) - Mike

[includeh10]

i appreciate your code: save many lines includeh10

[John R Shaw]

The only reasonable reason for formating you code like this class Cat { // codes }; is because the amount of space in published works (a.k.a books) is limited and you need to squeese the code so you can display it in less space. But formating your like this can lead to problems when debuging your code. I used this format some years back and I need to appoligise to anyone who is required to maintain it. Trust in the code Luke. Yea right!