Re: stdin and stdout

From	glen herrmannsfeldt <gah@ugcs.caltech.edu>
Newsgroups	comp.lang.c
Subject	Re: stdin and stdout
Date	2015-07-22 04:10 +0000
Organization	Aioe.org NNTP Server
Message-ID	<mon548$2ph$1@speranza.aioe.org> (permalink)
References	(1 earlier) <lnsi8ig09w.fsf@kst-u.example.com> <mojf3u$q45$1@dont-email.me> <lnbnf6fvsf.fsf@kst-u.example.com> <mojran$ccc$1@dont-email.me> <_zCrx.252825$152.91999@fx16.iad>

Show all headers | View raw

Richard Damon <Richard@damon-family.org> wrote:
> On 7/20/15 6:06 PM, Bartc wrote:

>> The problem is that there might be two C runtime libraries (one linked
>> normally, the other loaded independently at runtime). They could be
>> different libraries, or possibly the same one, but it thinks there are
>> two different instances of itself.

> This is getting off topic, but a program that staticly links to the 
> standard library and then uses a dynamic link library (at least on 
> windows) is inherently broken. The basic rule is if you use any DLL, 
> then you need to use the DLL version of the standard library (Which also 
> means that any DLL needs to use the DLL version of the standard library).

I suppose, but it happens sometimes. Consider the case where you
have two different libraries that are distributed object only, and
compiled with different compilers? It might be that each expects
a specific libc, so you need two of them. 

I also once mixed Fortran and C, and each had its own library.
That was before it was usual for the Fortran library to use C I/O.
Both buffer, and I/O gets mixed together.

-- glen

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