Re: Help understanding how winapi works
- From: Tim Roberts <timr@xxxxxxxxx>
- Date: Tue, 10 Jun 2008 22:39:06 -0700
ceh <cehupper@xxxxxxxxx> wrote:
Well, I suppose it's important to me the same way it's important to
the OS devs at MS.
My intent is to learn how the api works, not how to use the api
That's noble goal, but below a certain level, it doesn't help you to get
additional detail. Whether a particular API uses a linked list or a simple
array or a balanced tree to hold its requests is just not important. That's
called an "implementation detail", and if the detail changed, it wouldn't
change the operating system in any significant way.
There's all these internals books out there that do a lot of
Something happens
something else happens
A message is sent to the windows subsystem
Something else happens...
I want to know the "A message is sent to the windows subsystem" part.
To me, that is the most mysterious, most unexplained.
That kind of phrase is intentionally vague, because it means different
things at different times. Sometimes it means that a function is called.
Sometimes it means that a data structure gets added to a list. Sometimes
it means that a kernel call is made. Sometimes it means that an entry is
made in an array somewhere. The exact details depends on the exact API.
It is impossible to be more specific.
--
Tim Roberts, timr@xxxxxxxxx
Providenza & Boekelheide, Inc.
.
- References:
- Re: Help understanding how winapi works
- From: ceh
- Re: Help understanding how winapi works
- Prev by Date: Re: Help understanding how winapi works
- Next by Date: Re: virtual memory max size
- Previous by thread: Re: Help understanding how winapi works
- Next by thread: Re: Help understanding how winapi works
- Index(es):
Relevant Pages
|
