blocks|key|2190550|text|exit()退出整个程序，并报告传递给它的参数。这允许任何正在运行您的程序的程序找出错误退出的原因。(1可能意味着连接数据库失败，2可能意味着意外的参数，等等)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2190551|Return只返回你所在的当前函数，而不是整个程序。|2190552|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|$]]

exit() exits your entire program, and reports back the argument you pass it. This allows any programs that are running your program to figure out why it exited incorrectly. (1 could mean failure to connect to a database, 2 could mean unexpected arguments, etc).

Return only returns out of the current function you're in, not the entire program.

blocks|key|2190630|text|return基本上会从函数返回，并适当地调整堆栈指针以执行下一条指令，其中as+exit将导致程序本身终止。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2190631|在函数中使用exit()表示发生致命错误，程序无法恢复和继续，因此必须终止。|2190632|entityMap^0|0|6|14|4|0|6|6|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|R|8|@]|D|@]|E|$]]]|I|$]]

<code>return</code> will basically return from the function and adjust the stack pointers appropriately to execute the next instructions, where as <code>exit</code> will cause the program itself to terminate.

using <code>exit()</code> in a function indicates the fatal error and program cannot recover and continue and hence, it has to be terminated.

blocks|key|657155|text|exit不会从函数返回。它将从整个程序中退出|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|657156|entityMap^0|0|4|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

<code>exit</code> will not return from a function. It will exit from the entire program

blocks|key|656889|text|我不认为你想退出整个程序，对吧？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|656890|所以只要从函数返回就可以了。|656891|/*+This+would+happen+in+1+function+*/
+if(test+condition+1)
+{
++/*+something+went+wrong+*/
++return;+/*return+type+must+be+void+in+this+case+*/
+}

+if(test+condition+2)
+{
++++/*+something+went+wrong+with+another+condition*/
+++return;+/*return+type+must+be+void+in+this+case+*/
++}|code-block|syntax|javascript|656892|您还可以显式指定函数的返回类型，并使用返回值来判断是否一切正常。|656893|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I don't think you want to exit the entire program, right?

So just returning from the function would be fine. 

<pre><code>/* This would happen in 1 function */
 if(test condition 1)
 {
 /* something went wrong */
 return; /*return type must be void in this case */
 }

 if(test condition 2)
 {
 /* something went wrong with another condition*/
 return; /*return type must be void in this case */
 }
</code></pre>

You can also explicitly specify the return type of the function and use the return value to judge whether everything went fine or not.

blocks|key|1957722|text|您是在问我们是否应该从函数中返回错误代码？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1957723|嗯，这取决于你想为你的用户提供多大的信息量。如果您想表现得像软件一样，通常会弹出一个模式对话框，上面写着|1957724|1957725|发生了一些不好的事情！|blockquote|1957726|1957727|1957728|这样就不需要返回码了。|1957729|但是，如果您希望您的软件对用户有用，并让他们知道发生了什么，那么您最好提供某种诊断信息(至少是错误代码)。然后您可以弹出一条消息，上面写着：|1957730|1957731|我打不开"foo.bar“。|1957732|1957733|这个文件存在吗？你对它有读访问权吗？它是在网络共享上吗？也许我应该再试一次？|1957734|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|X|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|Y|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|10|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|11|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|12|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|O|3|P|5|G|7|14|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|15|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|16|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|U|$]]

You're asking us whether you should return error codes from your functions?

Well that depends upon how informative you want to be to your users. If you want to act like software usually acts and pop up a modal dialog that says

<blockquote>
 Something bad happened!
</blockquote>

Then there's no need for return codes.

If, however, you want to your software to be useful to your users and let them know what happened, then you better provide some kind of diagnostic information (error codes in the least). Then you can pop up a message that says:

<blockquote>
 I can't open "foo.bar".
 
 Does this file exist? Do you have read access to it? Is it on a network share? Maybe I should try again?
</blockquote>

blocks|key|2190748|text|通常这是为了让运行你的程序的程序能够做出一些明智的决定。例如，如果您的程序foo周围有一个包装器脚本，那么它可以使用变量$$检查退出参数并更改执行路径：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2190749|exec+foo+if+$$+eq+'0'：echo+"Success“elif+$$+eq+'2'：exec+error-recovery-script|2190750|或者，您可以自己执行echo+$$来查看程序的退出代码。|2190751|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Usually this is so that the program running your program can take some intelligent decisions.
For example if there is a wrapper script around your program foo, then it could check the 
exit argument using variable $$ and change the execution path:

exec foo
if $$ eq '0':
 echo "Success"
elif $$ eq '2':
 exec error-recovery-script

Alternatively, you yourself can execute echo $$ to see what was the exit code from the program.

blocks|key|1959779|text|如果您的想法是根据测试条件返回值，则更喜欢使用return而不是exit。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1959780|要返回1，而不是exit(+1+)，请使用return+1。|1959781|没有张贴原因，因为在这篇link中有关于同样的详细讨论。|offset|length|1959782|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/1116493/how-to-quit-a-c-program/1118826#1118826^0|0|0|C|4|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

If the idea is to return the value based on the test condition, prefer using return instead of exit.
To return 1, instead of exit(1), use return 1.
Not posting the reasons, as there was a detailed discussion for the same in this <a href="https://stackoverflow.com/questions/1116493/how-to-quit-a-c-program/1118826#1118826">link</a>.

linux gcc 4.4.1 C99

I am just wondering is there any advantage using the following techniques. I noticed with some code I was reading the exit number went up in value, as displayed in this code snippet. 

<pre><code>/* This would happen in 1 function */
if(test condition 1)
{
 /* something went wrong */
 exit(1);
}

if(test condition 2)
{
 /* something went wrong with another condition*/
 exit(2);
}
</code></pre>

or doing the following and just returning:

<pre><code>/* This would happen in 1 function */
if(test condition 1)
{
 /* something went wrong */
 return;
}

if(test condition 2)
{
 /* something went wrong with another condition*/
 return;
}
</code></pre>

using exit(1) to return from a function

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

linux gcc 4.4.1 C99我只是想知道使用下面的技术有什么好处。我注意到，在读取一些代码时，退出编号的值增加了，如下面的代码片段所示。/* This would happen in 1 function */if(test condition 1){    /* something went wrong */    exit(1);}if(test condition 2){    /

问使用exit(1)从函数返回
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用exit(1)从函数返回EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用exit(1)从函数返回
EN