ios developer tiny share-20161108

最新推荐文章于 2020-12-01 15:10:39 发布

zheng3stone

最新推荐文章于 2020-12-01 15:10:39 发布

阅读量229

点赞数

CC 4.0 BY-SA版权

分类专栏： ios developer tiny share 文章标签： ios objective-c Block Block作为方法参数 typedef定义Block类型

本文链接：https://blog.youkuaiyun.com/zheng3stone/article/details/53286643

ios developer tiny share 专栏收录该内容

93 篇文章

订阅专栏

本文介绍了Objective-C中Block作为方法参数的最佳实践，强调Block应置于方法参数列表的末尾，并通过示例展示了如何使用typedef简化Block的声明，提高代码可读性。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

今天继续讲Objective-C的Block，讲Block作为方法的参数，按照惯例，一般放到最后一个。另外，讲下使用typeof来定义Block，使得Block在语法上更加简洁、易读。

下面是ios reference官方的讲解：

A Block Should Always Be the Last Argument to a Method

It’s best practice to use only one block argument to a method. If the method also needs other non-block arguments, the block should come last:

- (void)beginTaskWithName:(NSString *)name completion:(void(^)(void))callback;

This makes the method call easier to read when specifying the block inline, like this:

[self beginTaskWithName:@"MyTask" completion:^{
	NSLog(@"The task is complete");
}];

Use Type Definitions to Simplify Block Syntax

If you need to define more than one block with the same signature, you might like to define your own type for that signature.

As an example, you can define a type for a simple block with no arguments or return value, like this:

typedef void (^XYZSimpleBlock)(void);

You can then use your custom type for method parameters or when creating block variables:

XYZSimpleBlock anotherBlock = ^{
	...
};

- (void)beginFetchWithCallbackBlock:(XYZSimpleBlock)callbackBlock {
    ...
    callbackBlock();
}

Custom type definitions are particularly useful when dealing with blocks that return blocks or take other blocks as arguments. Consider the following example:

void (^(^complexBlock)(void (^)(void)))(void) = ^ (void (^aBlock)(void)) {
    ...
    return ^{
        ...
    };
};

The complexBlock variable refers to a block that takes another block as an argument (aBlock) and returns yet another block.

Rewriting the code to use a type definition makes this much more readable:

XYZSimpleBlock (^betterBlock)(XYZSimpleBlock) = ^ (XYZSimpleBlock aBlock) {
    ...
    return ^{
        ...
    };
};