Function hangup

src/cmd.c:5158–5180

some very old systems, or descendents of such systems, expect signal handlers to have return type `int', but they don't actually inspect the return value so we should be safe using `void' unconditionally */ ARGUSED*/

   the return value so we should be safe using `void' unconditionally */
/*ARGUSED*/
void
hangup(
    int sig_unused UNUSED)   /* called as signal() handler, so sent
                              * at least one arg */
{
    if (program_state.exiting)
        program_state.in_moveloop = 0;
    nhwindows_hangup();
#ifdef SAFERHANGUP
    /* When using SAFERHANGUP, the done_hup flag is tested in rhack
       and a couple of other places; actual hangup handling occurs then.
       This is 'safer' because it disallows certain cheats and also
       protects against losing objects in the process of being thrown,
       but also potentially riskier because the disconnected program
       must continue running longer before attempting a hangup save. */
    program_state.done_hup++;
    /* defer hangup iff game appears to be in progress */
    if (program_state.in_moveloop
        && program_state.something_worth_saving)
        return;
#endif /* SAFERHANGUP */
    end_of_input();
}

void
end_of_input(void)