Comments on: XCode: The Starting Curly Brace http://scyanide.com/2010/02/xcode-the-starting-curly-brace/?utm_source=rss&utm_medium=rss&utm_campaign=xcode-the-starting-curly-brace My life, interests, and random babble... Thu, 26 Apr 2012 20:45:00 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Scyanide http://scyanide.com/2010/02/xcode-the-starting-curly-brace/comment-page-1/#comment-1990 Scyanide Thu, 26 Apr 2012 20:45:00 +0000 http://scyanide.com/?p=410#comment-1990 I found this searching around: http://stackoverflow.com/questions/5120343/xcode-4-with-opening-brace-on-new-line Seems XCode 4 changed a few things up and relies heavily on its built-in snippets for auto-completion. The marked answer goes into how to find and edit SystemCodeSnippets.codesnippets file. It has to be done manually at the moment. http://forrst.com/posts/Put_that_where_it_might_belong_Xcode-PNL Also, looks like this guy is giving out the modified file for people. Hope this helps. Thanks for pointing this out to me. I'll update this page to accommodate the changes in XCode 4. I found this searching around:
http://stackoverflow.com/questions/5120343/xcode-4-with-opening-brace-on-new-line

Seems XCode 4 changed a few things up and relies heavily on its built-in snippets for auto-completion. The marked answer goes into how to find and edit SystemCodeSnippets.codesnippets file. It has to be done manually at the moment.

http://forrst.com/posts/Put_that_where_it_might_belong_Xcode-PNL
Also, looks like this guy is giving out the modified file for people.

Hope this helps. Thanks for pointing this out to me. I’ll update this page to accommodate the changes in XCode 4.

]]> By: Scyanide http://scyanide.com/2010/02/xcode-the-starting-curly-brace/comment-page-1/#comment-1989 Scyanide Thu, 26 Apr 2012 20:36:41 +0000 http://scyanide.com/?p=410#comment-1989 That's interesting. I think I've heard of it being that way before but it never crossed my mind. I'm very picky with my alignments and feel that the curly brace on a newline helps with block readability and organization. I'm also not a big fan of embedding statements into 1 line. Prefer to separate it all for readability AND for debugging purposes. Luckily for us, it doesn't have much, if any, impact during runtime. That’s interesting. I think I’ve heard of it being that way before but it never crossed my mind. I’m very picky with my alignments and feel that the curly brace on a newline helps with block readability and organization. I’m also not a big fan of embedding statements into 1 line. Prefer to separate it all for readability AND for debugging purposes. Luckily for us, it doesn’t have much, if any, impact during runtime.

]]> By: Scyanide http://scyanide.com/2010/02/xcode-the-starting-curly-brace/comment-page-1/#comment-1988 Scyanide Thu, 26 Apr 2012 20:32:08 +0000 http://scyanide.com/?p=410#comment-1988 I was hoping it would still work for 4.3 but I'll look into it when I get a chance and put a update on this post. I have noticed that it no longer puts the curly brace on the newline for me but figured the setting was reset and I've been too lazy to fix it. I was hoping it would still work for 4.3 but I’ll look into it when I get a chance and put a update on this post. I have noticed that it no longer puts the curly brace on the newline for me but figured the setting was reset and I’ve been too lazy to fix it.

]]> By: Steve http://scyanide.com/2010/02/xcode-the-starting-curly-brace/comment-page-1/#comment-1985 Steve Thu, 26 Apr 2012 16:07:58 +0000 http://scyanide.com/?p=410#comment-1985 Being very old programmer from the late 70's (when I was very, very young) the argument I remember for putting the curly brace on following the statement had to do with publishing costs. Back in the old days, the source code was printed in the back of the books and this simple change saved pages of expensive printing. At the cost of maintenance of actual source. Since so many books took advantage of this space saving technique, scores of software engineers, programmers and hackers just followed along what they learned through example. Those that have programmed from a long time value the ease and consistency of the paper wasting technique to line up the block statements and avoid unnecessary confusion and the visible advantage of obvious block organization. At least that's how I remember it happening - as it has annoyed me for three plus decades. Being forced into a format inspired by non-programmers by any IDE... really, really bugs me. Being very old programmer from the late 70′s (when I was very, very young) the argument I remember for putting the curly brace on following the statement had to do with publishing costs. Back in the old days, the source code was printed in the back of the books and this simple change saved pages of expensive printing. At the cost of maintenance of actual source. Since so many books took advantage of this space saving technique, scores of software engineers, programmers and hackers just followed along what they learned through example. Those that have programmed from a long time value the ease and consistency of the paper wasting technique to line up the block statements and avoid unnecessary confusion and the visible advantage of obvious block organization. At least that’s how I remember it happening – as it has annoyed me for three plus decades. Being forced into a format inspired by non-programmers by any IDE… really, really bugs me.

]]> By: Steve http://scyanide.com/2010/02/xcode-the-starting-curly-brace/comment-page-1/#comment-1984 Steve Thu, 26 Apr 2012 16:01:40 +0000 http://scyanide.com/?p=410#comment-1984 Any solution for XCode 4.3... the described plist file no longer seems to exist. Any solution for XCode 4.3… the described plist file no longer seems to exist.

]]> By: whisk IT http://scyanide.com/2010/02/xcode-the-starting-curly-brace/comment-page-1/#comment-655 whisk IT Tue, 20 Sep 2011 08:49:13 +0000 http://scyanide.com/?p=410#comment-655 Very nice! I hadn't quite decided which I prefer, but was aware that there were very much two camps on this. On further reflection, I've decided that your readability argument is the winner for me. Thank you! Very nice!
I hadn’t quite decided which I prefer, but was aware that there were very much two camps on this. On further reflection, I’ve decided that your readability argument is the winner for me.
Thank you!

]]> By: Scyanide http://scyanide.com/2010/02/xcode-the-starting-curly-brace/comment-page-1/#comment-137 Scyanide Fri, 18 Feb 2011 07:20:58 +0000 http://scyanide.com/?p=410#comment-137 This "wasted space" has 0 impact on the code being executed. Putting the curly brace on a new line helps block off the code inside and improves readability. I highly doubt a person's IQ level has anything to do with where they place the curly brace. It all comes down to preference, however. Feel free to place it anywhere you want. Unless you work for a company that has standards on the format, in which case you have to do as they say. My experience has shown than many companies enforce newline curly braces for readability. This “wasted space” has 0 impact on the code being executed. Putting the curly brace on a new line helps block off the code inside and improves readability. I highly doubt a person’s IQ level has anything to do with where they place the curly brace.

It all comes down to preference, however. Feel free to place it anywhere you want. Unless you work for a company that has standards on the format, in which case you have to do as they say. My experience has shown than many companies enforce newline curly braces for readability.

]]> By: funny http://scyanide.com/2010/02/xcode-the-starting-curly-brace/comment-page-1/#comment-136 funny Fri, 18 Feb 2011 06:54:29 +0000 http://scyanide.com/?p=410#comment-136 Funny that the morons continue to desire so strongly doing things the stupid way rather than the K&R way good thing all source formatters and sensible defaults use K&R style so coders with IQs higher than 100 can unfuck the code created by the morons who waste space with braces on their own lines!!! Funny that the morons continue to desire so strongly doing things the stupid way rather than the K&R way
good thing all source formatters and sensible defaults use K&R style so coders with IQs higher than 100 can unfuck the code created by the morons who waste space with braces on their own lines!!!

]]> By: Objective-C Coding Style « The Joe Lake Blog – joeylakey.com http://scyanide.com/2010/02/xcode-the-starting-curly-brace/comment-page-1/#comment-40 Objective-C Coding Style « The Joe Lake Blog – joeylakey.com Sat, 15 Jan 2011 14:26:05 +0000 http://scyanide.com/?p=410#comment-40 [...] [1] XCode: The Starting Curly Brace [2]Google Objective-C Style Guide [3]Google C++ Style [...] [...] [1] XCode: The Starting Curly Brace [2]Google Objective-C Style Guide [3]Google C++ Style [...]

]]> By: Scyanide http://scyanide.com/2010/02/xcode-the-starting-curly-brace/comment-page-1/#comment-39 Scyanide Mon, 15 Nov 2010 16:55:34 +0000 http://scyanide.com/?p=410#comment-39 Thanks for the info. I'll have to check that tool out soon. Thanks. Thanks for the info. I’ll have to check that tool out soon. Thanks.

]]>