Programming Forums > Community Forums > Coder's Corner Lounge

bl00dninja · Jun 24th, 2006, 1:51 AM

the thread on lisp made me think of this, do you prefer:

if(blaah) {
       code here...
}

or:

(Toggle Plain Text)

else if(blahhhh)  {
       code here...  }

or:

(Toggle Plain Text)

else
    {
        code here...
    }

or something else?

personally, i prefer the last in most cases.

[/code]

v0id · Jun 24th, 2006, 1:56 AM

When I just started programming i did use the first method, but now i use the last.
You get a better view of your code, imo.

Jimbo · Jun 24th, 2006, 2:01 AM

I use the last, but I don't indent the braces

(Toggle Plain Text)

else
{
   // code here
}

Dameon · Jun 24th, 2006, 2:29 AM

I use the first. It saves a line. You get more code on the screen at once without a sacrifice of readability. I also omit braces whenever possible, and open/close them on one line when there's a one line method.

v0id · Jun 24th, 2006, 2:36 AM

Actually I don't only use the last, It's varying of the situation.
If I'm f.ex. making a class with a constructor there's initalizing a value I also make it on one line.

(Toggle Plain Text)

class myClass 
{
    private:
        std::string myString;
    public:
        myClass(){ myString = "Hey!"; }
        ~myClass(){};
};

Mocker · Jun 24th, 2006, 3:04 AM

2nd one for If statements up to 4 lines or so. Anything longer and I use the first or last. Last is best for readability if you dont mind whitespace.

Tedd · Jun 24th, 2006, 3:50 AM

I started PHP using the first, now I usually use the last.

nnxion · Jun 24th, 2006, 6:00 AM

Quote:

Originally Posted by Dameon

I use the first. It saves a line. You get more code on the screen at once without a sacrifice of readability. I also omit braces whenever possible, and open/close them on one line when there's a one line method.

I disagree, the readability is worse when trying to save a line in my opinion.

DaWei · Jun 24th, 2006, 7:41 AM

I began with the first and shifted to the last. I don't indent the brace (same as Jimbo). I think the first method sacrifices readability and leads to mismatches. I don't use braces for a one-liner block, but I recommend that novices do so until their facility increases. My idea about stylistic issues such as this can be seen in my sig.

InfoGeek · Jun 24th, 2006, 8:01 AM

I prefer the last one as I think it's more readable IMO.

Jun 24th, 2006, 1:51 AM	#1
bl00dninja Programming Guru Join Date: Oct 2004 Location: namespace std Posts: 1,246 Rep Power: 6	brace/paren matching scheme the thread on lisp made me think of this, do you prefer: (Toggle Plain Text) if(blaah) { code here... } if(blaah) { code here... } or: (Toggle Plain Text) else if(blahhhh) { code here... } else if(blahhhh) { code here... } or: (Toggle Plain Text) else { code here... } else { code here... } or something else? personally, i prefer the last in most cases. [/code] __________________ i put on my robe and wizard hat... Have you ever heard of Plato, Aristotle, Socrates?...Morons.

Jun 24th, 2006, 2:01 AM	#3
Jimbo Battle Programmer Join Date: Feb 2006 Location: Bellevue, WA, USA Posts: 773 Rep Power: 3	I use the last, but I don't indent the braces (Toggle Plain Text) else { // code here } else { // code here }

Jun 24th, 2006, 2:29 AM	#4
Dameon Troll Join Date: Apr 2005 Location: Texas Posts: 732 Rep Power: 4	I use the first. It saves a line. You get more code on the screen at once without a sacrifice of readability. I also omit braces whenever possible, and open/close them on one line when there's a one line method. __________________ MD5(sig) = bcef75433db02e9ad9bf81d6f7c5c270

Jun 24th, 2006, 2:36 AM	#5
v0id Hobbyist Programmer Join Date: Apr 2006 Posts: 155 Rep Power: 3	Actually I don't only use the last, It's varying of the situation. If I'm f.ex. making a class with a constructor there's initalizing a value I also make it on one line. (Toggle Plain Text) class myClass { private: std::string myString; public: myClass(){ myString = "Hey!"; } ~myClass(){}; }; class myClass { private: std::string myString; public: myClass(){ myString = "Hey!"; } ~myClass(){}; }; Last edited by v0id; Jun 24th, 2006 at 2:48 AM.

Jun 24th, 2006, 3:04 AM	#6
Mocker Hobbyist Programmer Join Date: Oct 2005 Location: Indiana Posts: 224 Rep Power: 0	2nd one for If statements up to 4 lines or so. Anything longer and I use the first or last. Last is best for readability if you dont mind whitespace. __________________ #programmingforums relay - http://thegupstudio.com/cgi-bin/pforelay.cgi freelance scripts - http://ryanguthrie.com/index.html

Jun 24th, 2006, 1:56 AM	#2
v0id Hobbyist Programmer Join Date: Apr 2006 Posts: 155 Rep Power: 3	When I just started programming i did use the first method, but now i use the last. You get a better view of your code, imo.

Jun 24th, 2006, 3:50 AM	#7
Tedd Newbie Join Date: Jun 2006 Location: New York. Posts: 11 Rep Power: 0	I started PHP using the first, now I usually use the last. __________________ The Blog The Webcomic

Jun 24th, 2006, 7:41 AM	#9
DaWei Resident Grouch Join Date: Jun 2005 Posts: 6,453 Rep Power: 10	I began with the first and shifted to the last. I don't indent the brace (same as Jimbo). I think the first method sacrifices readability and leads to mismatches. I don't use braces for a one-liner block, but I recommend that novices do so until their facility increases. My idea about stylistic issues such as this can be seen in my sig. __________________ Abstraction doesn't make it impossible to write bad code; it makes it possible to write superior code. Contributor's Corner: Grumpy on C++ Exceptions DaWei on Pointers

Jun 24th, 2006, 8:01 AM	#10
InfoGeek Professional Programmer Join Date: Jun 2005 Location: India, The great. Posts: 435 Rep Power: 4	I prefer the last one as I think it's more readable IMO. __________________ PFO - My daily dose of technology.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Programming Forums > Community Forums > Coder's Corner Lounge

brace/paren matching scheme