Newsgroups:	comp.os.msdos.djgpp
From:	manni DOT heumann AT gmx DOT de (Manni Heumann)
Subject:	Re: exit() makes my program crash!!!! (FINAL comment)
References:	<19991016090802 DOT 4896 DOT rocketmail AT web115 DOT yahoomail DOT com>
X-Newsreader:	News Xpress 2.01
Date:	Sat, 16 Oct 1999 10:48:37 GMT
NNTP-Posting-Host:	ppp36-275.hrz.uni-bielefeld.de
Message-ID:	<38085807.0@news.uni-bielefeld.de>
X-Trace:	16 Oct 1999 12:48:39 +0200, ppp36-275.hrz.uni-bielefeld.de
Lines:	37
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

In article <19991016090802 DOT 4896 DOT rocketmail AT web115 DOT yahoomail DOT com>, djgpp AT delorie DOT com wrote:
>
>Hello everyone,
>        how are u? fine?? good! :)
>                
>        well... regarding my previous problem (exit() causes
>my prog to freeze..) here is the last comment!
>
>        i have discovered that the program does NOT freeze!
>the program has actually finished! but screen did not
>return to text mode!! i became sure of this, as, after
>the program freezed, i just typed 'exit' and i simply
>returned back to windows!
>        This simply means that exit() does NOT always return
>back to text mode by itself! i HAVE to put the
>following line:
>        screen.settext();
>before ANY call to exit!!
>
>        is this considered a bug in exit()??? or this is
>normal??
>
>Thank you,
>Urs forever,
>        Mohamed El Dawy

The C-standard doesn't know anything about text or graphics mode. So exit 
doesn't have to no, either. If you do something non-standard like switching 
between these modes in your program, it seems fair that you are responsible to 
clean up afterwards.
So: No, I wouldn't consider that a bug.


--

Manni

- Raw text -