NetNews Usenet Archive 1992 #16/NN_1992_16.iso/spool/comp/os/msdos/apps/4122

Internet Message Format | 1992-07-27 | 1.8 KB

Path: sparky!uunet!mcsun!uknet!ox-prg!news
From: [e-mail]
Newsgroups: comp.os.msdos.apps
Subject: Turbo C 2.00 compiler
Summary: Possible bug in fwrite?
Keywords: Turbo C compiler
Message-ID: <[e-mail]>
Date: 27 Jul 92 12:50:12 GMT
References: <[e-mail]>
Sender: [e-mail]
Organization: Oxford University Computing Laboratory, UK
Lines: 29

(Clenched teeth question)
Does anyone know if the Turbo C 2.00 libraries have a bug in fwrite or
fread or fstat?

Detail: I wasn't able to run my compilation of the SSPELL14.ZIP
sources (simtel and mirrors) because of a consistent system crash
somewhere in a pair of short routines which do nothing but fwrite, fstat and
fread. Of course I can't tell which of these really is buggy
because of the bug, but I can work around it. The sources are
guaranteed by the author to be compilable under MICROSOFT C, and are
supposed to be portable, so he and I both would like to know. I have
successfully compiled and run them under K&R unix compilers.

I'd just like to know for sure, before I sue for wasted time.

Autres b\^etes noires:
And while we're on the subject of Turbo C compilation - does anyone
know (a) if the system(command) call supports (1) redirects (2) pipes in the
comamnd string sent to the OS? I vaguely recall a posting in some
related newsgroup on a library to support these features, so I suspect
not?

And (b) I see that the spawnxx(path,arg0,..) functions pass the complete
argument list to the called procedure, *including arg zero*. So that might
answer a thread a while back about how to call a program and fool it into
thinking its name is different. But the examples in the manual seem
contradictory here. Anyone know what the protocol really is?

Peter <[e-mail]>