From: Eli Zaretskii Newsgroups: comp.os.msdos.djgpp Subject: Re: fprintf() and using under graphic modes Date: Thu, 25 Nov 1999 10:08:11 +0200 Organization: NetVision Israel Lines: 25 Message-ID: References: <81hnbm$7jq$3 AT portraits DOT wsisiz DOT edu DOT pl> NNTP-Posting-Host: is.elta.co.il Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: news.netvision.net.il 943517199 5275 199.203.121.2 (25 Nov 1999 08:06:39 GMT) X-Complaints-To: abuse AT netvision DOT net DOT il NNTP-Posting-Date: 25 Nov 1999 08:06:39 GMT X-Sender: eliz AT is In-Reply-To: To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Thu, 25 Nov 1999, Damian Yerrick wrote: > > Thank you very much for that. All is need to be done is to check if this > > condition is true, and then decide to use fprintf or > > self_made_drawing_texts_func. > > The condition you need to check is > if(1) > self_made_drawing_texts_func() > else > printf_family_function() This is unfairly skewed, and IMHO does a misservice to those who asked for help in this matter. Using printf is certainly an alternative in some cases. For example, in a program that needs to work in both text and graphics modes, it might make a lot of sense to try to stick with printf if possible. There are other valid considerations as well, like the ability to redirect program's output to a file. Instead of ``selling'' your preferences, it is much better to describe the relative merits of the different alternatives and let the questor judge them.