blocks|key|2308614|text|从语法上讲，在那里放一个分号是可以的。它没有任何用处，而且也不鼓励这样做。一些编译器会对这个额外的分号给出警告。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2308615|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Grammatically it is OK to put a semicolon there. It serves no purpose, and it is discouraged to do that. Some compilers give warnings about this extra semicolon.

blocks|key|1903534|text|是的，它可以在XCode中工作和编译，没有副作用。我通常在从头部复制方法声明时意外地看到这一点，尽管我不建议有目的地将它们添加到方法的末尾。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1903535|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Yes it will work and compile with no side effects in XCode. I see it commonly done accidentally when copying the method declaration from the header, though I wouldn't recommend adding them to the end of methods purposefully.

blocks|key|3974293|text|是的，它将工作，但分号是不正确的，但它实际上不会导致任何崩溃。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3974294|Reference+link+here|offset|length|3974295|类的方法是在一对大括号内定义的，就像C函数一样。在大括号之前，它们的声明方式与接口文件中的相同，但没有分号。|3974296|entityMap|0|LINK|mutability|MUTABLE|url|http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/ObjectiveC/Chapters/ocDefiningClasses.html#//apple_ref/doc/uid/TP30001163-CH12-BAJHEIFE^0|0|0|J|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

Yes it will work, but the semi-colon is incorrect, however it won't actually cause any crashes.

<a href="http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/ObjectiveC/Chapters/ocDefiningClasses.html#//apple_ref/doc/uid/TP30001163-CH12-BAJHEIFE" rel="nofollow">Reference link here</a>

"Methods for a class are defined, like C functions, within a pair of braces. Before the braces, they’re declared in the same manner as in the interface file, but without the semicolon."

blocks|key|283089|text|是的，这样做的语法是可以接受的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|283090|事实上，我在我的实现中总是这样做，因为在接口之间复制和粘贴方法定义是很简单的，反之亦然，而不必记住您在哪里。我在单独的行上使用对齐的括号也很有帮助。|283091|Wil+Shipley+agrees+with+me+on+this|offset|length|283092|283093|以分号结束方法实现上的定义行，这样当它们更改时，您可以根据需要将它们复制-n-粘贴到您的标头(或文件顶部的“私有”类别)。分号在“接口”部分是必需的，但不会影响“实现”部分的任何内容。|blockquote|283094|283095|entityMap|0|LINK|mutability|MUTABLE|url|http://blog.wilshipley.com/2005/07/code-insults-mark-i.html^0|0|0|C|M|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@$F|X|G|Y|1|Z]]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|11|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

Yes, it is acceptable syntax to do this. 

In fact, I always do this in my implementations, because it then is trivial to copy and paste a method definition from interface to implementation and vice versa without having to remember where you are. It helps that I use aligned brackets on separate lines, as well.

Wil Shipley <a href="http://blog.wilshipley.com/2005/07/code-insults-mark-i.html" rel="noreferrer">agrees with me on this</a>:

<blockquote>
 End the definition lines on your
 method implementations with a
 semicolon, so you can copy-n-paste
 them to or from your header (or the
 "Private" category at the top of your
 file) as needed when they change.
 Semicolons are required in the
 "interface" section, but don't hurt
 anything in the "implementation"
 section.
</blockquote>

blocks|key|1903660|text|代码应该尽可能的干净和简单。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1903661|这不仅会增加代码中的垃圾，还会让人们(比如我)感到困惑，他们现在不得不花时间来看看这是不是一种有效的做法。|1903662|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Code should be as clean and simple as possible. 
Not only does this add litter to the code but confuses people (like me) who now have to spend the time to see if it is a valid practice.

blocks|key|3974779|text|我不确定这是什么时候引入的，但当您这样做时，会出现一个新的警告。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3974780|警告-方法-主体之前的分号|3974781|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I'm not sure when this was introduced, but there is a new warning raised when you do this.

warn-semicolon-before-method-body

<pre><code>- (void) designImageViewNow; {

//some code here

}
</code></pre>

Is it correct to write semicolon <code>;</code> just after the method name before body brackets in the implementation file objective-c.

Would this work?

As I am working on an iPhone app, I put the semicolon after the method name in one of my custom class by mistakenly. But there was no warning or any crash. In fact it is working fine.

Semicolon after the method name in Objective-C implementation file

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

- (void) designImageViewNow; {//some code here}在实现文件objective-c中，将分号;写在方法名称之后的正文括号之前是否正确。这样行得通吗？当我正在开发一个iPhone应用程序时，我错误地将分号放在了我的一个自定义类中的方法名之后。但没有任何警告或任何崩溃。事实上，它...

问Objective-C实现文件中方法名后的分号
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Objective-C实现文件中方法名后的分号EN