What is the significance of #pragma marks? Why do we need #pragma marks?

What is the purpose of #pragma marks in Xcode? Does their location in .m files matter? Should some #pragma come before all others?

• Do they have to be present?
• Can new marks be added? Why would they be? What causes it?
• Is there any harm in having a mark开发者_如何学Go removed? Would one ever want to?

#pragma mark directives show up in Xcode in the menus for direct access to methods. They have no impact on the program at all.

For example, using it with Xcode 4 will make those items appear directly in the Jump Bar.

There is a special pragma mark - which creates a line.

#pragma mark is used to tag the group of methods so you may easily find and detect methods from the Jump Bar. It may help you when your code files reach about 1000 lines and you want to find methods quickly through the category from the Jump box.

In a long program it becomes difficult to remember and find a method name. So pragma mark allows you to categorize methods according to the work they do. For example, you tagged some tag for Table View Protocol Methods, AlertView Methods, Init Methods, Declaration, etc.

#pragma mark is the facility for Xcode, but it has no impact on your code. It merely helps to make it easier to find methods while coding.

In simple words, we can say that #pragma mark - is used for categorizing methods, so you can find your methods easily. It is very useful for long projects.

Just to add the information I was looking for: pragma mark is Xcode specific, so if you deal with a C++ project that you open in different IDEs, it does not have any effect there. In Qt Creator, for example, it does not add categories for methods, nor generate any warnings/errors.

#pragma is a preprocessor directive which comes from C programming language. Its purpose is to specify implementation-dependent information to the compiler - that is, each compiler might choose to interpret this directive as it wants. That said, it is rather considered an extension which does not change/influence the code itself. So compilers might as well ignore it.

Xcode is an IDE which takes advantage of #pragma and uses it in its own specific way. The point is, #pragma is not Xcode and even Objective-C specific.

When we have a big/lengthy class, say more than a couple of 100s lines of code, we can't see everything on the monitor screen, hence we can't see the overview (also called document items) of our class. Sometime we want to see the overview of our class; all its methods, constants, properties, etc. at a glance. You can press Ctrl + 6 in Xcode to see overview of your class. You'll get a pop-up kind of window aka Jump Bar.

By default, this jump bar doesn't have any buckets/sections. It's just one long list. (Though we can just start typing when jump Bar appears and it will search among jump bar items.) Here comes the need of pragma mark.

If you want to create sections in your Jump Bar then you can use pragma marks with relevant description. Now refer to the snapshot attached in the question. There 'View lifeCycle' and 'A section dedicated ..' are sections created by pragma marks.

Use:

#pragma mark - NSSecureCoding

The main purpose of "pragma" is for developer reference.

You can easily find a method/function in a vast thousands of coding lines.

Xcode 11+:

Marker Line in Top

// MARK: - Properties

Marker Line in Top and Bottom

// MARK: - Properties -

Marker Line only in bottom

// MARK: Properties -