stdio.h ?

[\(ProteanThread\)]

can "stdio.h" be OS specific at the kernal level or ? i know what I'm
trying to ask here but not sure how to word it :-)
--
Woodzy
http://www.rtdos.com/forum

[Mark McIntyre]

On Tue, 8 Mar 2005 15:27:25 -0700, in comp.lang.c , "\(ProteanThrea d\)"
<sy***@rtdos.co m> wrote:

"Walter Roberson" <ro******@ibd.n rc-cnrc.gc.ca> wrote in message
news:d0******* *@canopus.cc.um anitoba.ca...

You could, but don't expect the result to be portable.

So in order to keep it portable I'd want to keep my own definitions separate
from the standard library ?

The only reason to supply your own stdio.h would be because you were
providing your own standard library.

Within the last couple of weeks, there was a thread here in comp.lang.c
to the effect that users are "prohibitte d from trying" to redefine
any routine in the standard library.

Thats correct - USERS are. The compiler writer isn't of course.
I was the lone holdout for

the interpretation that the standard didn't actually prohibit you
from trying: it just couldn't promise that anything would work
properly if you did.

If you're writing a compiler, you can and must supply a stdio.h, and
definitions for the funcions in it. If you're using a compiler, you must
not do it.
--
Mark McIntyre
CLC FAQ <http://www.eskimo.com/~scs/C-faq/top.html>
CLC readme: <http://www.ungerhu.com/jxh/clc.welcome.txt >

----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----

[Mark McIntyre]

On 8 Mar 2005 21:24:41 GMT, in comp.lang.c , ro******@ibd.nr c-cnrc.gc.ca
(Walter Roberson) wrote:

In article <1110314389.d45 27d3074cde45f4a ce6396d62a5df4@ teranews>,
\(ProteanThrea d\) <sy***@rtdos.co m> wrote:
:ok, few more questions:
:1. what's a tyger?

The old spelling of 'tiger'. On old maps, in places unknown and
potentially dangerous, it was supposedly common to put on the map,
"Beyond here be tygers."

:3. is "stdio.h" always necessary in plain C?

No! The C89 standard says in a footnote,
89. A header is not nessisarily a source file [...]

Whoa there! That doesn't mean its not necessary to *have* stdio.h. It means
its not necessarily a source file - neither more nor less. It could be in a
text library, built into the compiler itself, whatever. VAX C commonly puts
all the std headers into a text library which isn't human readable.
--
Mark McIntyre
CLC FAQ <http://www.eskimo.com/~scs/C-faq/top.html>
CLC readme: <http://www.ungerhu.com/jxh/clc.welcome.txt >

----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----

[\(ProteanThread\)]

"Mark McIntyre" <ma**********@s pamcop.net> wrote in message
news:ep******** *************** *********@4ax.c om...

If you're writing a compiler, you can and must supply a stdio.h, and
definitions for the funcions in it. If you're using a compiler, you must
not do it.
--

Is there such information on creating or defining a "stdio.h" file or whats
been accept as the standard arguments therein?

[\(ProteanThread\)]

"Mark McIntyre" <ma**********@s pamcop.net> wrote in message
news:ho******** *************** *********@4ax.c om...

or can I create my own "stdio.h" lib for my own OS ?

Of course
--

Thanks for your help.

[\(ProteanThread\)]

"Walter Roberson" <ro******@ibd.n rc-cnrc.gc.ca> wrote in message
news:d0******** **@canopus.cc.u manitoba.ca...

There is a 1999 international C standard. There are, though,
not a great number of compilers built for that standard yet.
--

So, since I'm obvioiusly new to this, does Borlands Turbo C 2.01 follow the
C89 Standard?

[\(ProteanThread\)]

"Mark McIntyre" <ma**********@s pamcop.net> wrote in message
news:ut******** *************** *********@4ax.c om...

Whoa there! That doesn't mean its not necessary to *have* stdio.h. It means its not necessarily a source file - neither more nor less. It could be in a text library, built into the compiler itself, whatever. VAX C commonly puts all the std headers into a text library which isn't human readable.
--

Thanks for the clarification.

[E. Robert Tisdale]

(ProteanThread) wrote:

1. what's a tyger?

Tyger! Tyger! burning bright
In the forests of the night,
What immortal hand or eye
Could frame thy fearful symmetry?

In what distant deeps or skies
Burnt the fire of thine eyes?
On what wings dare he aspire?
What the hand, dare seize the fire?

And what shoulder, & what art,
Could twist the sinews of thy heart?
And when thy heart began to beat,
What dread hand? & what dread feet?

What the hammer? what the chain?
In what furnace was thy brain?
What the anvil? what dread grasp
Dare its deadly terrors clasp?

When the stars threw down their spears,
And water'd heaven with their tears,
Did he smile his work to see?
Did he who made the Lamb make thee?

Tyger! Tyger! burning bright
In the forests of the night,
What immortal hand or eye
Dare frame thy fearful symmetry?

-- William Blake

[Mark McIntyre]

On Tue, 8 Mar 2005 16:48:32 -0700, in comp.lang.c , "\(ProteanThrea d\)"
<sy***@rtdos.co m> wrote:

Is there such information on creating or defining a "stdio.h" file or whats
been accept as the standard arguments therein?

The C standard defines what has to be in stdio.h.
--
Mark McIntyre
CLC FAQ <http://www.eskimo.com/~scs/C-faq/top.html>
CLC readme: <http://www.ungerhu.com/jxh/clc.welcome.txt >

[Mark McIntyre]

On Tue, 8 Mar 2005 16:50:08 -0700, in comp.lang.c , "\(ProteanThrea d\)"
<sy***@rtdos.co m> wrote:

So, since I'm obvioiusly new to this, does Borlands Turbo C 2.01 follow the
C89 Standard?

When was it written, and what does its documentation say? If you want a
better answer, you should ask in a borland group, since details of
individual compilers are offtopic here (and liable to be answered wrong
anyway, we're not the experts)

--
Mark McIntyre
CLC FAQ <http://www.eskimo.com/~scs/C-faq/top.html>
CLC readme: <http://www.ungerhu.com/jxh/clc.welcome.txt >

[Clark S. Cox III]

On 2005-03-08 19:11:10 -0500, Mark McIntyre <ma**********@s pamcop.net> said:

On Tue, 8 Mar 2005 16:48:32 -0700, in comp.lang.c , "\(ProteanThrea d\)"
<sy***@rtdos.co m> wrote:

Is there such information on creating or defining a "stdio.h" file or whats
been accept as the standard arguments therein?

The C standard defines what has to be in stdio.h.

Or, at least it defines what happens when the compiler encounters:
#include <stdio.h>

;)

--
Clark S. Cox, III
cl*******@gmail .com