Date: Thu, 7 Aug 2008 11:54:10 -0500 (CDT) From: "Sean C. Farley" <scf@FreeBSD.org> To: Gabor Kovesdan <gabor@kovesdan.org> Cc: fjoe@FreeBSD.org, hackers@FreeBSD.org Subject: Re: strange issue reading /dev/null Message-ID: <alpine.BSF.1.10.0808071150460.2133@thor.farley.org> In-Reply-To: <489B22BD.5050109@kovesdan.org> References: <489B0ACD.80008@kovesdan.org> <alpine.BSF.1.10.0808071058020.1056@thor.farley.org> <489B22BD.5050109@kovesdan.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 7 Aug 2008, Gabor Kovesdan wrote:
> Sean C. Farley ha scritto:
>> You are testing c which has not been set. It works OK if you set c
>> then do the test:
>>
>> + c = fgetc(f);
>> if (c != EOF)
>> - printf("%c\n", fgetc(f));
>> + printf("%c\n", c);
> Yes, you are right, this is what I meant, I'm just a bit
> disorganised....
> Thanks!
You are welcome.
Actually, what I found odd was that the base gcc did not warn about
using an uninitialized variable using -Wall.
Obviously, test fopen() and fgetc() return codes correctly as others
have noted. I just assume you were not in your test program.
Sean
--
scf@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.1.10.0808071150460.2133>