Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #161511
| From | James Kuyper <jameskuyper@alumni.caltech.edu> |
|---|---|
| Newsgroups | comp.lang.c |
| Subject | Re: Calling exit in main |
| Date | 2021-06-25 14:59 -0400 |
| Organization | A noiseless patient Spider |
| Message-ID | <sb592j$3a0$1@dont-email.me> (permalink) |
| References | <sb3sbt$j9a$1@dont-email.me> <sb4u2n$cls$1@dont-email.me> <sb51ds$1hr3$1@gioia.aioe.org> <sb58ib$nj4$1@dont-email.me> |
On 6/25/21 2:50 PM, James Kuyper wrote:
> On 6/25/21 12:48 PM, Guillaume wrote:
>> Le 25/06/2021 à 17:51, James Kuyper a écrit :
>>> I think "return 0;" is conceptually simpler, but keep in mind that
>>>
>>> "a return from the initial call to the main function is equivalent to
>>> calling the exit function with the value returned by the main function
>>> as its argument;" (5.1.2.2.3)
>>>
>>> Therefore, the net effect is almost the same.
>>
>> Sorry, but I'm not sure I understand the "almost" here.
>>
>> According to the standard, that you quoted, both are supposed to be
>> equivalent. At least on a conforming implementation.
>>
>> If, on some implementation, they are actually not equivalent, then
>> wouldn't this be non-conforming?
>>
>> Lastly, maybe we need to know what exactly "equivalent" means in this
>> context. Is the term properly defined in the standard? (Because for all
>> I know, you seem to be assuming here that "equivalent" could imply
>> "almost the same" - almost meaning: not quite.)
>
> I think the equivalence described in 5.1.2.2.3 is exact; the "almost" in
> my statement is a consequence of that exact equivalence, not a result of
> thinking it might be less than exact.
>
> There's an important difference between calling exit() from inside of
> main(), and calling exit() after main() has returned, using the value
> returned by main(): all objects with automatic storage duration declared
> inside of main() that are in scope at the point where the return
> statement gets executed end their lifetime as soon as it gets executed,
> before any exit handlers have a chance to execute. If a function has
> been registered with atexit() that refers to such an object, that
> function will have undefined behavior. That would not be the case if
> exit() were called inside of main().
>
> Referring to such an object from within an exit handler is little
> tricky, but far from impossible. Here's the simplest example I could
> think of:
>
> int *pint;
I accidentally sent this message first as a Thunderbird "Reply" to
Guillaume's personal e-mail. When I corrected that mistake by re-sending
it as a "Followup", I accidentally dropped the rest of my example:
void exit_handler(void) {
// Do something with *pint
}
int main(void) {
int i;
pint = &i;
atexit(exit_handler);
exit(0);
}
I think it makes a lot of sense for Thunderbird to distinguish between
"Reply" and "Followup" - they should have done so from the beginning.
However, I've spent more than a decade getting used to hitting "Reply"
when I wanted to post a Followup, and it's proving very difficult for me
to break that habit.
Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Calling exit in main Mehdi Amini <atorrses@gmail.com> - 2021-06-25 10:46 +0430
Re: Calling exit in main Kli-Kla-Klawitter <kliklaklawitter69@gmail.com> - 2021-06-25 08:19 +0200
Re: Calling exit in main Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2021-06-25 00:48 -0700
Re: Calling exit in main Kli-Kla-Klawitter <kliklaklawitter69@gmail.com> - 2021-06-25 10:08 +0200
Re: Calling exit in main Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2021-06-25 01:38 -0700
Re: Calling exit in main Kli-Kla-Klawitter <kliklaklawitter69@gmail.com> - 2021-06-25 11:03 +0200
Re: Calling exit in main Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2021-06-25 08:27 -0700
Re: Calling exit in main Kli-Kla-Klawitter <kliklaklawitter69@gmail.com> - 2021-06-25 18:52 +0200
Re: Calling exit in main Kaz Kylheku <563-365-8930@kylheku.com> - 2021-06-25 17:14 +0000
Re: Calling exit in main scott@slp53.sl.home (Scott Lurndal) - 2021-06-25 18:17 +0000
Re: Calling exit in main Kaz Kylheku <563-365-8930@kylheku.com> - 2021-06-25 18:48 +0000
Re: Calling exit in main Real Troll <real.troll@trolls.com> - 2021-06-25 20:21 +0100
Re: Calling exit in main Kli-Kla-Klawitter <kliklaklawitter69@gmail.com> - 2021-06-26 09:21 +0200
Re: Calling exit in main Kaz Kylheku <563-365-8930@kylheku.com> - 2021-06-28 16:45 +0000
Re: Calling exit in main Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-06-28 18:14 +0100
Re: Calling exit in main Richard Damon <Richard@Damon-Family.org> - 2021-06-25 13:33 -0400
Re: Calling exit in main Kaz Kylheku <563-365-8930@kylheku.com> - 2021-06-25 15:05 +0000
Re: Calling exit in main Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2021-06-25 01:34 -0700
Re: Calling exit in main James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-06-25 11:51 -0400
Re: Calling exit in main Kaz Kylheku <563-365-8930@kylheku.com> - 2021-06-25 16:13 +0000
Re: Calling exit in main Guillaume <message@bottle.org> - 2021-06-25 18:48 +0200
Re: Calling exit in main Kaz Kylheku <563-365-8930@kylheku.com> - 2021-06-25 17:05 +0000
Re: Calling exit in main Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2021-06-25 15:22 -0600
Re: Calling exit in main Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2021-06-25 15:29 -0600
Re: Calling exit in main James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-06-25 14:50 -0400
Re: Calling exit in main James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-06-25 14:59 -0400
Re: Calling exit in main Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2021-06-25 13:40 -0700
Re: Calling exit in main Jens Schweikhardt <usenet@schweikhardt.net> - 2021-06-26 08:25 +0000
Re: Calling exit in main Andrey Tarasevich <andreytarasevich@hotmail.com> - 2021-06-25 10:42 -0700
Re: Calling exit in main James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-06-25 14:51 -0400
csiph-web