Re: Re: NULL Device ?

"Thilo Köhler" <[email protected]> Thu, 27 Oct 2005 11:15:55 +0200 (MEST)
Newsgroups gmane.comp.windows.ce.freeware
Message-ID <[email protected]>
Hello All!

Thank you so far for your help, but that is not
really what I need.
I will explain it more carfully:

I have a lot of fprintf (stdout,"blabla");
in my (huge) sourcecode.
To get the output, I open a file and store
the filehandle in - lets say - FILE* wince_debugout
Then I do a 
#undefine stdout
#define wince_debugout stdout

Now all the output goes to this file.
But I want a version without this output, to not create
a lot of file accesses.
The simpliest solution seems to me, that I open instead of
"\Temp\mylogfile.txt" a null device like "\dev\nul".
But I did not find something like this for WinCE.
I want neighter a console, nor an invalid file, that
would result in a null pointer. 

I can not patch the fprintf command, because sometimes
I need fprintf to write into files. I only want to eleminate
fprintf's that go to stdout and stderr.

Greetings,

Thilo

-- 
Telefonieren Sie schon oder sparen Sie noch?
NEU: GMX Phone_Flat http://www.gmx.net/de/go/telefonie

[Non-text portions of this message have been removed]



------------------------ Yahoo! Groups Sponsor --------------------~--> 
Get Bzzzy! (real tools to help you find a job). Welcome to the Sweet Life.
http://us.click.yahoo.com/A77XvD/vlQLAA/TtwFAA/W4wwlB/TM
--------------------------------------------------------------------~->