Should we indent with 2 spaces? about objective-c-style-guide

[gregheo]

👍

I code with two-space indentation all the time so I'm in. My own personal preference aside though, I think our page width restrictions are a good practical reason.

[hollance]

I'm OK with 2 spaces for the book but I find 4 spaces reads much easier and on the website there's less concern for wrapping because you can scroll the code blocks.

That said, we should just use a tool to reformat code according to these guidelines before putting them into the tutorials. That way authors can simply write in the style they want and the tool will fix everything up.

[funkyboy]

I agree on this.
A script can take care of indentation.
Maybe we need one also for curly braces?

method {}
vs
method {
}

Cesare Rocchi
studiomagnolia.com

On Nov 7, 2013, at 7:07 PM, Matthijs Hollemans [email protected] wrote:

I'm OK with 2 spaces for the book but I find 4 spaces reads much easier and on the website there's less concern for wrapping because you can scroll the code blocks.

That said, we should just use a tool to reformat code according to these guidelines before putting them into the tutorials. That way authors can simply write in the style they want and the tool will fix everything up.

—
Reply to this email directly or view it on GitHub.

There are tools that handle this already, so no need to write a script. But if you think 4 spaces is nicer than 2, well I have to rethink everything I've ever thought about you, hollance. ;)

[hollance]

I can't be held responsible for what other people think about me. :-)

And yes, I meant using one of the existing pretty printer tools.

[rwenderlich]

+1 vote for 2 spaces, as I think it is better for our purposes on raywenderlich.com (conserving space in print/books so we have as little line wraps as possible, which waste space, don't look good, and are harder to read). I put a pull request for this, but if we decide to go forward with this a bunch of the examples in the guide will need to be switched from 4->2 as well.