K&R Style

gordingin wrote:
Is there a way to turn this off, it is SO 1978.....

What are you talking about? K & R is probably still supported, but there is nothing to turn off. Just don't write code that way.

gordingin wrote:
Certainly but the UI formats it like that... just old school

I'm sorry, but I must repeat myself. What are you talking about? Can you provide any examples of automatically-generated UI code using K & R?

Select C99 in Project Settings will turn it off.

gordingin wrote:
Create a class....

No, not good enough! What on earth are you talking about? Do you know what K & R C is?

CharlieCL wrote:
Select C99 in Project Settings will turn it off.

Turn what off? Have I been living under an Xcode rock for ten years?

OK. Let's take a step back here. We are getting nowhere and taking forever to get there. This thread is almost a month old. Let's wrap it up.

K & R Style C refers to the C language as defined in the 1st edition of Kernighan and Ritchie's C Programming Language book. The following is correct K & R C syntax:

#include <stdio.h>
foo(str, value)
 char * str; int value;
 {
 printf("String: %s, int: %d ", str, value);
 return value;
 }

Any C compiler should accept this without errors. The 2nd edition of Kernighan and Ritchie's book was based on the new "ANSI" version of C. The biggest change is the funky function definition.

Classes did not exist in either version of the C programming language.

I have not seen K & R "in the wild" since the first and last time I wrote some in 1997 when I was working on a project for a customer who wanted it done in "C", and not that new-fangled "ANSI" version. I wrote a very nice object-oriented K & R C program for him.

So, can you explain, by way of a concrete example, what you are talking about? Please, no more 3 word responses.

gordingin wrote:
I thought K&R was

int foo() {
}

that FIRST bracket...

I like it like

int foo()
{
}

Oh no. That is just style. In fact, the style:

int foo() {
}

is probably the most preferred/common style, I'm sorry to say. I agree with you. I actually prefer:

int foo()
 {
 }

but I can live with

int foo()
{
}

This one really bugs me

int foo() {
}

Alas, we are in the minority.

You might like this little thing I put together: http://etresoft.org/etrecode.html

You can also edit the Xcode text macros: http://developer.apple.com/mac/library/documentation/DeveloperTools/Conceptual/X codeWorkspace/100-TheText_Editor/text_editor.html#//appleref/doc/uid/TP40002679-SW43

You can fix that issue by changing some default settings for XCode - see http://developer.apple.com/mac/library/documentation/DeveloperTools/Reference/Xc odeUserDefaultRef/100-XcodeUserDefaults/UserDefaultRef.html

You probably want to use

defaults write com.apple.Xcode XCCodeSenseFormattingOptions -dict BlockSeparator " "

Andreas