Outline a general structure for #pragma marks

[jspahrsummers]

A stab at #19.

Rendered Markdown

[dannygreg]

Good start. I think I would prefer life cycle at the very top, followed by property overrides.

[joshaber]

That's fine with me 👍

[jspahrsummers]

@dannygreg Any reason for the preference? This structure more closely matches how we've been writing our interfaces, I think.

[dannygreg]

@jspahrsummers Not really… if it lumps overridden accessors and the likes of @synchronized together. We tend to do the overrides randomly further down (below the lifecycle at least).

[jspahrsummers]

I'm not sure what you're referring to with @synchronized.

I meant that this matches the order we typically declare things in header files, not how we've been doing implementations so far.

[alanjrogers]

I used to prefer to have the lifecycle first, but in a post ARC world I think it makes sense to have property overrides first (after where @synthesize used to be).

That being said I can go either way on this, as long as they are near each other.

[dannygreg]

@jspahrsummers bah! Totally glossed over that. I still think it's weird having property accessors ahead of lifecycle.

I have near zero reasoning for that though :/.

[jspahrsummers]

I've basically preferred property overrides at the top because it does put @synthesize, @dynamic, and any modified accessors all together, like @alanjrogers says.

It'd be weird to move either of the former two below Lifecycle, IMO, and I'd rather keep them together.

[jspahrsummers]

Any ripostes to the above?

[joshaber]

0.01 fudges given.

[dannygreg]

Nope, the case has been made well.

[jspahrsummers]

Cool, then I'm just gonna self-merge this.