Groups | Search | Server Info | Login | Register
| From | Tim Rentsch <tr.17687@z991.linuxsc.com> |
|---|---|
| Newsgroups | comp.std.c |
| Subject | Re: Function calls |
| Date | 2023-10-04 19:21 -0700 |
| Organization | A noiseless patient Spider |
| Message-ID | <86bkdddd20.fsf@linuxsc.com> (permalink) |
| References | <calls-20231004163135@ram.dialup.fu-berlin.de> |
ram@zedat.fu-berlin.de (Stefan Ram) writes: > A recent draft of the C specification says about "return": > > |A return statement terminates execution of the current > |function and returns control to its caller. > > . There's also a section "Function calls" in a recent draft. > I expect that this section says something similar, to the effect that > during the evaluation of a function call, control is transferred to > the called function, but I was not able to find such wording! AFAICT the C standard does not say explicitly that a function call gives or transfers control to the function being called. It has been pointed out that the standard does say that calling a function suspends execution of the current block. Considering those facts, do you think there is a problem with the current wording used in the standard? If you do, what would you say the problem is, and why is it a problem?
Back to comp.std.c | Previous | Next — Next in thread | Find similar
Re: Function calls Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-10-04 19:21 -0700
Re: Function calls James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-10-05 20:50 -0700
Re: Function calls Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-10-06 05:38 -0700
Re: Function calls James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-10-06 18:04 -0700
Re: Function calls Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-10-08 15:30 -0700
csiph-web