blocks|key|4092371|text|函数原型是用于外部函数的。我的规则是每个非静态函数都有一个原型，除了main()。我使用'-Wmissing-prototypes‘的GCC选项。通常，它捕获的是当我忘记声明一个函数静态的时候。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4092372|同样，在C中以这种方式声明函数：|4092373|void+function(void);|code-block|syntax|javascript|4092374|而不是这样：|4092375|void+function();|4092376|因为第二种方法意味着该函数接受未指定数量的参数，这并不是您想要的(这是为了与ANSI+C之前的版本兼容)。|4092377|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

Function prototypes are for external functions. My rule is that every non-static function gets a prototype, except main(). I use the '-Wmissing-prototypes' GCC option. Usually what it catches is when I forget to declare a function static.

Also, declare functions in C this way:

<pre><code>void function(void);
</code></pre>

And not this way:

<pre><code>void function();
</code></pre>

Because the second way means that the function takes an unspecified number of parameters, which isn't what you want (it's for compatibility with pre-ANSI C).

blocks|key|4092248|text|No。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|4092249|我甚至不知道这在严格的ansi+c中是否合法。|4092250|entityMap^0|0|2|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

No.

And I don't know if it is even legal in strict ansi c.

blocks|key|32|text|当应用于函数原型时，“代码改变很多”也是一种糟糕的代码味道。如果接口(函数签名)变化很大，那么函数的职责可能不是很清楚。首先，弄清楚如何将问题划分为子责任，然后才开始编写代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|33|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|$]]

"Code changes a lot" when applied to function prototypes is also a bad code smell. If the interface (function signature) changes a lot, the responsibilities of a function are probabaly not very clear. First work to figure out how to divide the problem to subresponsibilities and only after that start to write code.

blocks|key|874059|text|“所以，也许它只是少了一行要编辑的内容？”|type|unstyled|depth|inlineStyleRanges|entityRanges|data|874060|这是唯一可能的“好处”，在这种情况下，纯粹的懒惰。|874061|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|$]]

"so maybe it's just one less line to edit?"

That's the only possible "benefit" in this case, plain laziness.

blocks|key|4092212|text|更少的代码修改是我能想到的唯一“优势”。通常这只是“懒惰”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4092213|在任何情况下，缺点都更加明显:你必须将所有函数都放在一个源文件中；函数在源文件中的顺序现在很重要，等等。另外，其他人在查看/时会感到困惑，因为头文件的做法是.c+file...best+.h+it。|4092214|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|$]]

Less code to change is the only 'advantage' I can think of. Typically this is just 'lazy'

In any event, the disadvantages are more significant: you've gotta have the functions all in one source file; order of functions in the source file now matters, etc. Also, other people will be confused looking at/for the header file...best practice is to .c and .h it.

blocks|key|4092121|text|我看到的唯一好处是，您不必每次更改函数本身时都更新函数原型。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4092122|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|$]]

the only benefit I see is that you don't have to update the function prototypes each time you change the functions themselves.

blocks|key|1303130|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1303131|代码更改很多，所以可能只是少了一行要编辑的代码？|blockquote|1303132|1303133|1303134|我猜这就是原因。我想不出任何其他原因--编译速度(实际上)和执行时间都没有变化，只有更新代码的时间。|1303135|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|J|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|K|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|L|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|M|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|N|7|@]|8|@]|9|$]]|$1|H|3|-4|4|5|6|O|7|@]|8|@]|9|$]]]|I|$]]

<blockquote>
 The code changes a lot, so maybe it's
 just one less line to edit?
</blockquote>

I'd guess that's the reason. I can't think of any other reason - neither does the compilation speed change (practically), nor the execution time, merely the time for updating the code.

blocks|key|1300852|text|我能想到的唯一优点是，它使您不必将函数的第一行复制并粘贴到.c或.h文件的prototypes部分。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1300853|对于在其他文件中引用的函数，您别无选择，只能有一个原型。|1300854|对于具有文件作用域的函数(即静态函数)，将所有原型放在文件顶部的块中是很有用的。这样，任何静态函数都可以被该文件中任何位置的另一个函数调用。如果没有原型，函数A()只能在代码中声明了B()的情况下才能调用函数B()。|1300855|此外，如果作用域中没有原型，一些编译器会对参数做出不安全的假设。|1300856|此外，如果您编写的代码必须符合MISRA-C，则要求所有函数在作用域中都有一个原型。|1300857|我还主张确保原型包含参数名称，而不仅仅是它们的类型(这是合法的)，因为它只是通过查看原型来阐明参数的用途。|1300858|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

The only advantage I can think of is that it saves you having to copy and paste the first line of the function into the prototypes section of your .c or .h file.

For functions which are referenced in other files, you have no choice but to have a prototype.

For functions with file scope (i.e. static functions), it's useful to have all the prototypes in a block at the top of the file. That way, any static function can be called by another from anywhere in that file. Without prototypes, function A() can only call function B() if B() is declared above it in the code.

Also, some compilers will make unsafe assumptions about parameters if there's no prototype in scope.

In addition, if you write code which has to conform to MISRA-C, it's a requirement that all functions have a prototype in scope.

I'd also advocate ensuring that the prototype contains the parameter names, not just their types (which is legal), as it clarifies the purpose of the parameters just by looking at the prototype.

blocks|key|1303249|text|它的打字量更少，所以可能会降低RSI的风险。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1303250|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|$]]

It's less typing, so maybe that reduces your risk for RSI.

I'm working with some C code that does not contain function prototypes for a certain class of functions. Are there any advantages to not using function prototypes? The functions never call each other and have no parameters. The code changes a lot, so maybe it's just one less line to edit?

Are there any benefits to NOT using function prototypes in C?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我正在使用一些不包含某类函数的函数原型的C代码。不使用函数原型有什么好处吗？这些函数从不互相调用，也没有参数。代码更改了很多，所以可能只是少了一行要编辑的代码？

问在C中不使用函数原型有什么好处吗？
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在C中不使用函数原型有什么好处吗？EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在C中不使用函数原型有什么好处吗？
EN