Re: stdin and stdout

From	Bartc <bc@freeuk.com>
Newsgroups	comp.lang.c
Subject	Re: stdin and stdout
Date	2015-07-23 09:27 +0100
Organization	A noiseless patient Spider
Message-ID	<moq8ds$8o9$1@dont-email.me> (permalink)
References	(3 earlier) <lnbnf6fvsf.fsf@kst-u.example.com> <mojran$ccc$1@dont-email.me> <HqGdndXgDcf6fTPInZ2dnUU7-WudnZ2d@posted.internetamerica> <monq6h$55g$1@dont-email.me> <D_ydnW-bf6ZAoC3InZ2dnUU7-QOdnZ2d@posted.internetamerica>

Show all headers | View raw

On 23/07/2015 02:05, Gordon Burditt wrote:
>>>> The stdin/stdout in your code will only correspond to one of those. If
>>>> you call the fprintf of one library, with the stdout of the other, I
>>>> don't know what will happen.
>
> Call the fprintf wrapper in one library, which calls fprintf in the
> real standard C library.
>
>>> It's a waste of time to find out, so delete the executable instead
>>> of trying to run it.  Such a program doesn't always crash immediately;
>>> sometimes it just throws in some uninitialized memmory garbage
>>> instead.
>>
>> This comes up when trying to use a dynamic version of a C runtime
>> library via a different language, or a different version of C.
>
> If you are writing another standard C library, you're doing something
> wrong.  *CALL THE EXISTING ONE*.  Writing a wrapper library is fine.

This and the rest of your comments suggest you've either completely 
misunderstood the problem, or I've explained it very badly.

I'm not rewriting any C library (although that might be one solution!). 
I needed to obtain stdin/stdout by non-conventional means. Why, you'll 
have to re-read the thread.


-- 
Bartc

Thread

stdin and stdout Bartc <bc@freeuk.com> - 2015-07-20 14:37 +0100
  Re: stdin and stdout Richard Heathfield <rjh@cpax.org.uk> - 2015-07-20 14:58 +0100
    Re: stdin and stdout Bartc <bc@freeuk.com> - 2015-07-20 15:31 +0100
      Re: stdin and stdout Ben Bacarisse <ben.usenet@bsb.me.uk> - 2015-07-20 16:29 +0100
        Re: stdin and stdout Bartc <bc@freeuk.com> - 2015-07-20 17:03 +0100
      Re: stdin and stdout Ken Brody <kenbrody@spamcop.net> - 2015-07-20 12:09 -0400
      Re: stdin and stdout Lőrinczy Zsigmond <zsiga@nospam.for.me> - 2015-07-21 10:02 +0200
  Re: stdin and stdout Keith Thompson <kst-u@mib.org> - 2015-07-20 11:19 -0700
    Re: stdin and stdout Bartc <bc@freeuk.com> - 2015-07-20 19:38 +0100
      Re: stdin and stdout Keith Thompson <kst-u@mib.org> - 2015-07-20 12:56 -0700
        Re: stdin and stdout Bartc <bc@freeuk.com> - 2015-07-20 23:06 +0100
          Re: stdin and stdout glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-07-20 23:18 +0000
            Re: stdin and stdout BGB <cr88192@hotmail.com> - 2015-07-21 14:12 -0500
          Re: stdin and stdout gordonb.9oj0u@burditt.org (Gordon Burditt) - 2015-07-21 19:14 -0500
            Re: stdin and stdout Bartc <bc@freeuk.com> - 2015-07-22 11:11 +0100
              Re: stdin and stdout gordonb.3xos3@burditt.org (Gordon Burditt) - 2015-07-22 20:05 -0500
                Re: stdin and stdout Bartc <bc@freeuk.com> - 2015-07-23 09:27 +0100
          Re: stdin and stdout Richard Damon <Richard@Damon-Family.org> - 2015-07-21 21:44 -0400
            Re: stdin and stdout glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-07-22 04:10 +0000
      Re: stdin and stdout BGB <cr88192@hotmail.com> - 2015-07-21 12:55 -0500
        Re: stdin and stdout Bartc <bc@freeuk.com> - 2015-07-21 20:49 +0100
          Re: stdin and stdout BGB <cr88192@hotmail.com> - 2015-07-22 00:05 -0500
            Re: stdin and stdout "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-07-22 02:48 -0700
              Re: stdin and stdout "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-07-22 02:57 -0700
                Re: stdin and stdout gordonb.bjmxp@burditt.org (Gordon Burditt) - 2015-07-22 20:27 -0500
              Re: stdin and stdout BGB <cr88192@hotmail.com> - 2015-07-22 13:19 -0500
                Re: stdin and stdout Robert Wessel <robertwessel2@yahoo.com> - 2015-07-22 18:09 -0500

csiph-web