Objective-C编程指南：Cocoa开发基石

需积分: 3 62 浏览量更新于2024-07-31 收藏 1.15MB PDF 举报

Objective-C编程语言是一门由Apple Inc.在2010年发布的面向Mac平台的关键技术，专为Xcode开发工具集而设计。这本《The Objective-C Programming Language》提供了深入浅出的介绍，旨在帮助开发者掌握Objective-C的语法和Cocoa框架的运用。本书的核心知识点包括： 1. **Objective-C语法**：作为Objective-C的基础，学习者将了解其面向对象编程特性，如类（Class）、对象（Object）、继承（Inheritance）、消息传递（Message Passing）和协议（Protocol）。Objective-C结合了C语言的灵活性和Smalltalk的动态性，允许程序员以更自然的方式与系统交互。 2. **Cocoa编程**：Cocoa是Apple开发的用于构建图形用户界面（GUI）的框架，它基于Objective-C。Cocoa应用广泛应用于Mac OS X和iOS平台上，提供了一套强大的API，涵盖了窗口管理、视图层次结构、数据绑定、以及各种内置组件如NSWindow、NSView和NSViewController的使用。 3. **工具与环境**：书中会介绍如何在Xcode环境中进行Objective-C开发，包括创建项目、设置构建流程、调试代码和使用Xcode的智能提示和自动补全功能。 4. **版权和许可**：文档强调了所有内容的版权归属，禁止任何形式的复制、存储或传输，除非获得Apple Inc.的书面许可。此外，对于苹果商标和特定快捷键的使用有严格的限制，以保护知识产权和避免商标侵权。 5. **知识产权保护**：虽然本书提供了技术指导，但并未授予任何技术许可，Apple保留所有与此文档描述技术相关的知识产权。读者只能在个人使用时存储文档，并为个人目的打印文档，必须保留版权声明。《The Objective-C Programming Language》是一本实用的教程，适合想要深入学习Objective-C编程并利用Cocoa进行Mac应用开发的人员。通过阅读这本书，开发者可以建立起坚实的编程基础，掌握现代苹果平台开发的关键技能。

For methods with multiple arguments, Objective-C's method names are interleaved with the arguments such

that the method’s name naturally describes the arguments expected by the method. The imaginary message

below tells the myRectangle object to set its origin to the coordinates (30.0, 50.0):

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

arguments

A selector name includes all the parts of the name, including the colons, so the method is named

setOriginX:y:. It has two colons as it takes two arguments. The selector name does not, however, include

anything else, such as return type or parameter types.

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.

In principle, the Rectangle class could instead implement a setOrigin:: which would be invoked as follows:

[myRectangle setOrigin:30.0 :50.0]; // This is a bad example of multiple 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.

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 19).

Object Messaging

CHAPTER 1

Objects, Classes, and Messaging

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.

■ 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.

Object Messaging 17

CHAPTER 1

Objects, Classes, and Messaging

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.

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.

Object Messaging

CHAPTER 1

Objects, Classes, and Messaging

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.

Dynamic Method Resolution

You can provide implementations of class and instance methods at runtime using dynamic method resolution.

See Dynamic Method Resolution in the Objective-C Runtime Programming Guide for more details.

Dot Syntax

Objective-C provides a dot (.) operator that offers a compact and convenient syntax you can use as an

alternative to square bracket notation ([]s) to invoke accessor methods. It is particularly useful when you

want to access or modify a property that is a property of another object (that is a property of another object,

and so on).

Using the Dot Syntax

Overview

You can use the dot syntax to invoke accessor methods using the same pattern as accessing structure

elements as illustrated in the following example:

myInstance.value = 10;

printf("myInstance value: %d", myInstance.value);

The dot syntax is purely “syntactic sugar”—it is transformed by the compiler into invocation of accessor

methods (so you are not actually accessing an instance variable directly). The code example above is exactly

equivalent to the following:

[myInstance setValue:10];

printf("myInstance value: %d", [myInstance value]);

General Use

You can read and write properties using the dot (.) operator, as illustrated in the following example.

Listing 1-1 Accessing properties using the dot syntax

Graphic *graphic = [[Graphic alloc] init];

Object Messaging 19

CHAPTER 1

Objects, Classes, and Messaging

NSColor *color = graphic.color;

CGFloat xLoc = graphic.xLoc;

BOOL hidden = graphic.hidden;

int textCharacterLength = graphic.text.length;

if (graphic.textHidden != YES) {

graphic.text = @"Hello";

}

graphic.bounds = NSMakeRect(10.0, 10.0, 20.0, 120.0);

(@"Hello" is a constant NSString object—see “Compiler Directives” (page 118).)

Accessing a property property calls the get method associated with the property (by default, property) and

setting it calls the set method associated with the property (by default, setProperty:). You can change the

methods that are invoked by using the Declared Properties feature (see “Declared Properties” (page 67)).

Despite appearances to the contrary, the dot syntax therefore preserves encapsulation—you are not accessing

an instance variable directly.

The following statements compile to exactly the same code as the statements shown in Listing 1-1 (page

19), but use square bracket syntax:

Listing 1-2 Accessing properties using bracket syntax

Graphic *graphic = [[Graphic alloc] init];

NSColor *color = [graphic color];

CGFloat xLoc = [graphic xLoc];

BOOL hidden = [graphic hidden];

int textCharacterLength = [[graphic text] length];

if ([graphic isTextHidden] != YES) {

[graphic setText:@"Hello"];

}

[graphic setBounds:NSMakeRect(10.0, 10.0, 20.0, 120.0)];

An advantage of the dot syntax is that the compiler can signal an error when it detects a write to a read-only

property, whereas at best it can only generate an undeclared method warning that you invoked a non-existent

setProperty: method, which will fail at runtime.

For properties of the appropriate C language type, the meaning of compound assignments is well-defined.

For example, you could update the length property of an instance of NSMutableData using compound

assignments:

NSMutableData *data = [NSMutableData dataWithLength:1024];

data.length += 1024;

data.length *= 2;

data.length /= 4;

which is equivalent to:

[data setLength:[data length] + 1024];

[data setLength:[data length] * 2];

[data setLength:[data length] / 4];

There is one case where properties cannot be used. Consider the following code fragment:

id y;

Object Messaging

CHAPTER 1

Objects, Classes, and Messaging

剩余136页未读，继续阅读

yymjl

粉丝: 0
资源: 2

Objective-C编程指南：Cocoa开发基石

The Objective-C Programming Language.pdf

objective-c programming language

The Objective-C Programming Language-2006.pdf

The Objective-C Programming Language (Apple Developer)

面向对象编程和Objective-C语言Object-Oriented Programming And The Objective-C Language

数据手册-SN75176B-datasheet.zip

基于javaswing酒店点餐系统

WinPE-26241.5000-ReFS-v3.14.wim

Kubernetes系统精讲 Go语言实战K8S集群可视化--第8章 【核心知识+原理分析】将应用和配置分离.zip

节能减排商品类别.doc

最新资源

Kubernetes系统精讲 Go语言实战K8S集群可视化--第8章【核心知识+原理分析】将应用和配置分离.zip