stdio.h？ [英] stdio.h ?

问题描述

可以stdio.h是核心的操作系统或？我知道我在这里问什么，但是不知道该如何说出来： - >

-

Woodzy
http://www.rtdos.com/forum

解决方案

对不起，您可以尝试改写帖子吗？我很确定很多人愿意回答你的问题。

在comp.lang.c" \（ ProteanThread\）" < SY *** @ rtdos.com>写道：

canstdio.h是核心的操作系统或？我知道我在这里问什么，但不知道如何说出来： - ）

什么意思是核心的操作系统级" ;?如果你有一个名为stdio.h的内核

标题它与用于用户程序的

同名文件无关。而userland标题也取决于操作系统特定的属性，编译器和libc，因此它不会与stdio.h相同。你得到一个不同的系统/
编译器/ libc组合。

问候，Jens

-

\\ \\ Jens Thoms Toerring ___ Je***********@physik.fu -berlin.de

\ __________________________ http：// www .toerring.de

[来自comp.lang.c; fups set]


2005年3月8日星期二，（ProteanThread）写道：

可以stdio.h是核心的操作系统或？我知道我在这里问什么，但不知道如何说出来： - ）

你的意思是，'是什么'里面" < stdio.h中> ;?答案就这个

新闻组而言（即，就标准C语言而言，b
而言）是：无论执行者是什么感觉。可以完全是

高级别的东西;可以是机器专用装配的线和线

代码;可能是一堆Unix系统调用;可能是粉红色的大象
芭蕾舞短裙的b $ b。我们不知道< stdio.h> "看起来"就像在你的系统上一样，并且我们不在乎。你也不需要关心，如果你正在做的就是用B语言编写程序。


如果你的实现很像其他实现，你会实际在硬盘上某处有一个名为stdio.h的文本文件。

如果你能找到它，打开它并看看。你可能会发现

，它充满了奥术，基本上难以理解的伪C，在好笑的地方有很多下划线。不要问我们这是什么意思;我们

我不知道。 （或者更确切地说，我们中的一些人可能确实知道这对我们/系统来说是什么意思

，但可能对你的系统不知道 - 而且，如果

我们开始向你解释实现内部，然后我们将不得不向每个人解释实现内部结构，并且有/数百/

的实现，所有不管怎么说，再也不会讨论C了。）


底线：< stdio的实现。 h取代;包含tygers。这个

新闻组并没有谈论tygers。但如果您对

有疑问，请使用< stdio.h>或者它定义的标准库函数，

这绝对是值得问的地方。


HTH，

-Arthur

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

解决方案

Sorry, could you try to reword your post. I am quite sure many would
like to answer your question.

In comp.lang.c "\(ProteanThread\)" <sy***@rtdos.com> wrote:

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 :-)

What means "OS specific at the kernal level"? If you have a kernel
header named "stdio.h" it got nothing to do with the file of the
same name used for userland programs. And the userland header also
depends on OS specific properties, the compiler and the libc, so it
won''t be identical to a "stdio.h" you get for a different system/
compiler/libc combination.
Regards, Jens
--
\ Jens Thoms Toerring ___ Je***********@physik.fu-berlin.de
\__________________________ http://www.toerring.de

[posting from comp.lang.c; fups set]

On Tue, 8 Mar 2005, (ProteanThread) wrote:

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 :-)

You mean, what''s "inside" <stdio.h>? The answer, as far as this
newsgroup is concerned (i.e., as far as the standard C language is
concerned) is: Whatever the implementor feels like. Could be completely
high-level stuff; could be lines and lines of machine-specific assembly
code; could be a bunch of Unix system calls; could be pink elephants
in tutus. We don''t know what <stdio.h> "looks" like on your system, and
we don''t care. You don''t need to care, either, if all you''re doing is
writing programs in C.

If your implementation is like many other implementations, you''ll
actually have a text file somewhere on your hard disk called "stdio.h".
If you can find it, open it up and take a look. You''ll probably find
out that it''s full of arcane, basically incomprehensible pseudo-C with
lots of underscores in funny places. Don''t ask us what it means; we
don''t know. (Or rather, some of us probably do know what it all means
on /our/ systems, but may have no idea about yours --- and besides, if
we start explaining implementation internals to you, then we''ll have to
explain implementation internals to everyone, and there are /hundreds/
of of implementations out there, all different. And then there wouldn''t
be any room here to talk about C anymore.)

Bottom line: The implementation of <stdio.h> contains tygers. This
newsgroup doesn''t talk about tygers. But if you have questions about
how to use <stdio.h> or the standard library functions it defines,
this is definitely the place to ask.

HTH,
-Arthur

这篇关于stdio.h？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！