Re: CRT and Win32 SDK
Actually, an implementation of the C runtime library doesn't need to
"use the OS". Consider embedded deivces without an OS. It's simply
an implementation of the standard-prescribed functions. In reality
most such implementations rely on an OS to provide some of the
functionality of course.
OP's confusion is that the C runtime library is part of the language
and one can't develop without it. It is part of the language standard,
true, but one can happily develop code without using it. It is _not_
part of the language. Both the user-mode Win32 API and the kernel
are indeed written mosly in C and to the best of my knowledge both
don't use a single function of the C runtime as defined by the C99
standard.
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://vcfaq.mvps.org
=====================================
"Alf P. Steinbach" <alfps@start.no> wrote in message
news:ybqdnUqrEPybnKnVnZ2dnUVZ_tDinZ2d@posted.comnet...
* SD:
So, what is this layer of "C" called?
Huh?
I should have phrased that better. What I mean is that the "C" used to
develop Win32 APIs must exist in some DLL.
Double huh. A language does not exist in a DLL.
...basically there must be an implementation of this for the Win32 APIs to
make use of.
Triple huh.
It's quite obvious that you have some severe misconception about
something, but as long as you refer to things as "this" it's impossible to
grok what you mean, and it's no good to engage in guessing game, sorry.
Try to look up Wikipedia on "runtime library". A runtime library uses the
operating system to implement some functionality that the runtime library
provides, e.g. thread-safe access to strtok. The operating system does
not use a runtime library. "A" uses "B". "B" does not use "A".
Cheers, & hth.
- Alf
--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?