Re: stdin ? stdin ? What's wrong with stdin?
From: Frank Hickman [MVP] (fhickman_NOSP_at_M_noblesoft.com)
Date: 02/17/05
- Next message: William DePalo [MVP VC++]: "Re: IO Completion Ports"
- Previous message: Tom Widmer: "Re: EOL Detection (Anyone?)"
- In reply to: Norman Bullen: "Re: stdin ? stdin ? What's wrong with stdin?"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 17 Feb 2005 13:03:19 -0500
"Norman Bullen" <norm@BlackKittenAssociates.com.INVALID> wrote in message
news:wH1Rd.2515$IU.2340@newsread3.news.pas.earthlink.net...
> Frank Hickman [MVP] wrote:
>>
>>
>> stdin, stdout and stderr are FILE* streams that are created and opened
>> when the CRT initializes a console application, they are not macros.
>> Have you included the proper header file in the module that is reporting
>> this?
>>
>>
>>
> Actually, stdin, stdout, and stderr ARE macro.
>
> #define stdin (&_iob[0])
> #define stdout (&_iob[1])
> #define stderr (&_iob[2])
>
> Macro expansion results in an expression that is a FILE * but the names
> stdin, etc. are not visible in the debugger because they are macros.
>
> Norm
>
> --
> --
> To reply, change domain to an adult feline.
>
DOH! That's what I get for assuming...
-- ============ Frank Hickman Microsoft MVP NobleSoft, Inc. ============ Replace the _nosp@m_ with @ to reply.
- Next message: William DePalo [MVP VC++]: "Re: IO Completion Ports"
- Previous message: Tom Widmer: "Re: EOL Detection (Anyone?)"
- In reply to: Norman Bullen: "Re: stdin ? stdin ? What's wrong with stdin?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|