🚀 go-pugleaf

In article <4dkvjk$6q5@lyra.csx.cam.ac.uk> nmm1@cus.cam.ac.uk (Nick
Maclaren) writes:

    [...]
> However, for the advanced paper, think about the following problems:
> 
> What is the effect of an atexit() function calling exit()?  Does it
> restart the atexit() queue, carry on as if the function had returned
> or does it abandon the atexit() queue?
> 
> I chose to do the second, as by far the most user-friendly, but I
> would NEVER write serious code that relied upon that action!
> 
> main() calls setjmp() and then calls exit().  An atexit() function
> calls longjmp() and returns to main().  This repeats (or does it?)
> 
> This is ALSO permitted by omission, but a good run-time system will
> trap it, issue an error message and stop without calling more atexit()
> functions.

According to ISO 9899: "If more than one call to the exit function is
executed by a program, the behavior is undefined."
-- 
James Kanze           (+33) 88 14 49 00          email: kanze@gabi-soft.fr
GABI Software, Sarl., 8 rue des Francs Bourgeois, 67000 Strasbourg, France
Conseils, études et réalisations en logiciel orienté objet --
              -- A la recherche d'une activité dans une region francophone