Objective-C编程语言官方指南

需积分: 9 95 浏览量更新于2024-07-30 收藏 1.15MB PDF 举报

"ObjC.pdf官方文档 - The Objective-C Programming Language" Objective-C是一种面向对象的编程语言，主要在苹果的开发工具中使用，特别是在iOS和macOS应用程序开发中扮演着核心角色。这份官方文档详细介绍了Objective-C的基础知识和高级特性。 1. **Chapter 1 Objects, Classes, and Messaging** - 对象：Objective-C中的所有数据都是对象，它们是类的实例。 - 类：定义了对象的结构和行为。 - 消息传递：Objective-C通过消息传递实现方法调用，它将方法名作为消息发送给对象，对象决定如何响应。 2. **Chapter 2 Defining a Class** - 类的定义：如何使用`@interface`和`@implementation`关键字来创建类。 - 继承：Objective-C支持单继承，子类可以继承父类的属性和方法。 - 实例变量：用于存储对象状态的数据。 3. **Chapter 3 Allocating and Initializing Objects** - 分配内存：使用`alloc`和`init`方法创建新对象。 - 初始化：确保对象在使用前被正确设置。 4. **Chapter 4 Protocols** - 协议：类似于接口，定义了一组方法声明，可以被多个类实现，支持多态性。 - 代理模式：常用协议实现，用于对象间通信。 5. **Chapter 5 Declared Properties** - 声明属性：提供自动内存管理、存取方法和合成属性的声明，简化编码。 6. **Chapter 6 Categories and Extensions** - 类别：添加方法到已存在的类，不增加实例变量。 - 扩展：在编译时向类添加私有接口。 7. **Chapter 7 Associative References** - 关联对象：允许对象在运行时动态地附加额外的信息，而无需扩展类的结构。 8. **Chapter 8 Fast Enumeration** - 快速枚举：高效遍历集合对象（如数组、字典）的方法。 9. **Chapter 9 Enabling Static Behavior** - 静态行为：如何使某些方法在编译时解析，提高性能。 10. **Chapter 10 Selectors** - 选择器：Objective-C中的消息标识符，表示方法的名字。 11. **Chapter 11 Exception Handling** - 异常处理：异常是程序运行时的错误，Objective-C提供了异常处理机制。 12. **Chapter 12 Threading** - 多线程：并发执行任务，提升应用性能和用户体验。 13. **Chapter 13 Remote Messaging** - 远程消息：通过进程间通信（IPC）在不同进程间的对象之间发送消息。 14. **Chapter 14 Using C++ With Objective-C** - C++与Objective-C的混合编程：Objective-C可以无缝集成C++代码，利用C++的强类型和模板等特性。这份文档不仅适合初学者，也对有经验的开发者有价值，因为它深入讲解了Objective-C的各个方面，帮助开发者理解和充分利用这种强大的编程语言。

[receiver message]

The receiver is an object, and the message tells it what to do. In source code, the message is simply the name

of a method and any arguments that are passed to it. When a message is sent, the runtime system selects

the appropriate method from the receiver’s repertoire and invokes it.

For example, this message tells the myRectangle object to perform its display method, which causes the

rectangle to display itself:

[myRectangle display];

The message is followed by a “;” as is normal for any line of code in C.

The method name in a message serves to “select” a method implementation. For this reason, method names

in messages are often referred to as selectors.

Methods can also take parameters, or “arguments.” A message with a single argument affixes a colon (:) to

the selector name and puts the argument right after the colon. This construct is called a keyword; a keyword

ends with a colon, and an argument follows the colon, as shown in this example:

[myRectangle setWidth:20.0];

A selector name includes all keywords, including colons, but does not include anything else, such as return

type or parameter types. The imaginary message below tells the myRectangle object to set its origin to the

coordinates (30.0, 50.0):

[myRectangle setOrigin:30.0 :50.0]; // This is a bad example of multiple arguments

Since the colons are part of the method name, the method is named setOrigin::. It has two colons as it

takes two arguments. This particular method does not interleave the method name with the arguments and,

thus, the second argument is effectively unlabeled and it is difficult to determine the kind or purpose of the

method’s arguments.

Instead, method names should interleave the name with the arguments such that the method's name naturally

describes the arguments expected by the method. For example, the Rectangle class could instead implement

a setOriginX:y: method that makes the purpose of its two arguments clear:

[myRectangle setOriginX: 30.0 y: 50.0]; // This is a good example of multiple

arguments

Object Messaging

CHAPTER 1

Objects, Classes, and Messaging

Important: The sub-parts of the method name—of the selector—are not optional, nor can their order be

varied. “Named arguments” and “keyword arguments” often carry the implication that the arguments to a

method can vary at runtime, can have default values, can be in a different order, can possibly have additional

named arguments. This is not the case with Objective-C.

For all intents and purposes, an Objective-C method declaration is simply a C function that prepends two

additional arguments (see Messaging in the Objective-C Runtime Programming Guide). This is different from

the named or keyword arguments available in a language like Python:

def func(a, b, NeatMode=SuperNeat, Thing=DefaultThing):

pass

where Thing (and NeatMode) might be omitted or might have different values when called.

Methods that take a variable number of arguments are also possible, though they’re somewhat rare. Extra

arguments are separated by commas after the end of the method name. (Unlike colons, the commas aren’t

considered part of the name.) In the following example, the imaginary makeGroup: method is passed one

required argument (group) and three that are optional:

[receiver makeGroup:group, memberOne, memberTwo, memberThree];

Like standard C functions, methods can return values. The following example sets the variable isFilled to

YES if myRectangle is drawn as a solid rectangle, or NO if it’s drawn in outline form only.

BOOL isFilled;

isFilled = [myRectangle isFilled];

Note that a variable and a method can have the same name.

One message expression can be nested inside another. Here, the color of one rectangle is set to the color of

another:

[myRectangle setPrimaryColor:[otherRect primaryColor]];

Objective-C also provides a dot (.) operator that offers a compact and convenient syntax for invoking an

object’s accessor methods. This is typically used in conjunction with the declared properties feature (see

“Declared Properties” (page 67)), and is described in “Dot Syntax” (page 20).

Sending Messages to nil

In Objective-C, it is valid to send a message to nil—it simply has no effect at runtime. There are several

patterns in Cocoa that take advantage of this fact. The value returned from a message to nil may also be

valid:

■ If the method returns an object, then a message sent to nil returns 0 (nil), for example:

Person *motherInLaw = [[aPerson spouse] mother];

If aPerson’s spouse is nil, then mother is sent to nil and the method returns nil.

■ If the method returns any pointer type, any integer scalar of size less than or equal to sizeof(void*),

a float, a double, a long double, or a long long, then a message sent to nil returns 0.

Object Messaging 17

CHAPTER 1

Objects, Classes, and Messaging

■ If the method returns a struct, as defined by the Mac OS X ABI Function Call Guide to be returned in

registers, then a message sent to nil returns 0.0 for every field in the data structure. Other struct data

types will not be filled with zeros.

■ If the method returns anything other than the aforementioned value types the return value of a message

sent to nil is undefined.

The following code fragment illustrates valid use of sending a message to nil.

id anObjectMaybeNil = nil;

// this is valid

if ([anObjectMaybeNil methodThatReturnsADouble] == 0.0)

{

// implementation continues...

}

Note: The behavior of sending messages to nil changed slightly with Mac OS X v10.5.

On Mac OS X v10.4 and earlier, a message to nil also is valid, as long as the message returns an object, any

pointer type, void, or any integer scalar of size less than or equal to sizeof(void*); if it does, a message

sent to nil returns nil. If the message sent to nil returns anything other than the aforementioned value

types (for example, if it returns any struct type, any floating-point type, or any vector type) the return value

is undefined. You should therefore not rely on the return value of messages sent to nil unless the method’s

return type is an object, any pointer type, or any integer scalar of size less than or equal to sizeof(void*).

The Receiver’s Instance Variables

A method has automatic access to the receiving object’s instance variables. You don’t need to pass them to

the method as arguments. For example, the primaryColor method illustrated above takes no arguments,

yet it can find the primary color for otherRect and return it. Every method assumes the receiver and its

instance variables, without having to declare them as arguments.

This convention simplifies Objective-C source code. It also supports the way object-oriented programmers

think about objects and messages. Messages are sent to receivers much as letters are delivered to your home.

Message arguments bring information from the outside to the receiver; they don’t need to bring the receiver

to itself.

A method has automatic access only to the receiver’s instance variables. If it requires information about a

variable stored in another object, it must send a message to the object asking it to reveal the contents of

the variable. The primaryColor and isFilled methods shown above are used for just this purpose.

See “Defining a Class” (page 35) for more information on referring to instance variables.

Polymorphism

As the examples above illustrate, messages in Objective-C appear in the same syntactic positions as function

calls in standard C. But, because methods “belong to” an object, messages behave differently than function

calls.

Object Messaging

CHAPTER 1

Objects, Classes, and Messaging

In particular, an object can be operated on by only those methods that were defined for it. It can’t confuse

them with methods defined for other kinds of object, even if another object has a method with the same

name. This means that two objects can respond differently to the same message. For example, each kind of

object sent a display message could display itself in a unique way. A Circle and a Rectangle would respond

differently to identical instructions to track the cursor.

This feature, referred to as polymorphism, plays a significant role in the design of object-oriented programs.

Together with dynamic binding, it permits you to write code that might apply to any number of different

kinds of objects, without you having to choose at the time you write the code what kinds of objects they

might be. They might even be objects that will be developed later, by other programmers working on other

projects. If you write code that sends a display message to an id variable, any object that has a display

method is a potential receiver.

Dynamic Binding

A crucial difference between function calls and messages is that a function and its arguments are joined

together in the compiled code, but a message and a receiving object aren’t united until the program is

running and the message is sent. Therefore, the exact method that’s invoked to respond to a message can

only be determined at runtime, not when the code is compiled.

The precise method that a message invokes depends on the receiver. Different receivers may have different

method implementations for the same method name (polymorphism). For the compiler to find the right

method implementation for a message, it would have to know what kind of object the receiver is—what

class it belongs to. This is information the receiver is able to reveal at runtime when it receives a message

(dynamic typing), but it’s not available from the type declarations found in source code.

The selection of a method implementation happens at runtime. When a message is sent, a runtime messaging

routine looks at the receiver and at the method named in the message. It locates the receiver’s implementation

of a method matching the name, “calls” the method, and passes it a pointer to the receiver’s instance variables.

(For more on this routine, see Messaging in the Objective-C Runtime Programming Guide.)

This dynamic binding of methods to messages works hand-in-hand with polymorphism to give object-oriented

programming much of its flexibility and power. Since each object can have its own version of a method, a

program can achieve a variety of results, not by varying the message itself, but by varying just the object

that receives the message. This can be done as the program runs; receivers can be decided “on the fly” and

can be made dependent on external factors such as user actions.

When executing code based upon the Application Kit, for example, users determine which objects receive

messages from menu commands like Cut, Copy, and Paste. The message goes to whatever object controls

the current selection. An object that displays text would react to a copy message differently from an object

that displays scanned images. An object that represents a set of shapes would respond differently from a

Rectangle. Since messages don’t select methods (methods aren’t bound to messages) until runtime, these

differences are isolated in the methods that respond to the message. The code that sends the message

doesn’t have to be concerned with them; it doesn’t even have to enumerate the possibilities. Each application

can invent its own objects that respond in their own way to copy messages.

Objective-C takes dynamic binding one step further and allows even the message that’s sent (the method

selector) to be a variable that’s determined at runtime. This is discussed in the section Messaging in the

Objective-C Runtime Programming Guide.

Object Messaging 19

CHAPTER 1

Objects, Classes, and Messaging

剩余136页未读，继续阅读

xiuzhaoyang

粉丝: 5

Objective-C编程语言官方指南

objc.io最新集合系列《Functional Swift》等五本图书

Objective-C编程语言详解与应用

Objective-C编程入门教程

ObjC.pdf 英文

ObjC(English).pdf

OBJC-APP-Arch.pdf

objc app架构.pdf

swifter-tips.pdf

iOS 中的 NSTimer.pdf

ios开发快捷键大全.pdf

最新资源