c++ questions.

[chy1013m1]

so far i've learned from various sources about c++'s high level
abilities, such as how to use c++ to solve topcoder problems, write a
binary search tree, pointers, stacks queues.etcetc.
But where does c++ fit in, say, in driver development? I've always saw
people saying c++'s low level abilities ( or C ) on the internet, but I
have no idea how pointer is a low level tool ( other than modifying a
block of memory if wanted) About manipulating memory with pointers,
doen't OS shield one app from another when app launches( in protected
mode flat model)? than how is pointer useful in that way? through the
use of OS API?
thanks!

[Your Uncle]

<ch*******@gmail.com> wrote in message
news:11**********************@r2g2000cwb.googlegro ups.com...

so far i've learned from various sources about c++'s high level
abilities, such as how to use c++ to solve topcoder problems, write a
binary search tree, pointers, stacks queues.etcetc.
But where does c++ fit in, say, in driver development? I've always saw
people saying c++'s low level abilities ( or C ) on the internet, but I
have no idea how pointer is a low level tool ( other than modifying a
block of memory if wanted) About manipulating memory with pointers,
doen't OS shield one app from another when app launches( in protected
mode flat model)? than how is pointer useful in that way? through the
use of OS API?

I think you answered your own question there. They won't talk about the API
around here but they will tell you about the c++ part of working with it
when you come with a specific question. Unless you experience a different
usenet than I do, you'll find it hard to find people who have good advice to
give on APIs (these guys prefer to work for money). cheers, f

[Julián Albo]

ch*******@gmail.com wrote:

But where does c++ fit in, say, in driver development? I've always saw
people saying c++'s low level abilities ( or C ) on the internet, but I
have no idea how pointer is a low level tool ( other than modifying a
block of memory if wanted) About manipulating memory with pointers,
doen't OS shield one app from another when app launches( in protected

In many operating systems a driver is not an app. And how to write drivers
is very specific of each. Thus, better ask in newsgroups about your
favorite operating systems.

--
Salu2

Inviato da X-Privat.Org - Registrazione gratuita http://www.x-privat.org/join.php

[Phlip]

chy1013m1 wrote:

so far i've learned from various sources about c++'s high level
abilities
Oh, like STL, parsing, locales, etc.?
such as how to use c++ to solve topcoder problems, write a
binary search tree, pointers, stacks queues.etcetc.
Those are low level. Feel free to learn them, but on a job use them
sparingly. Go to STL first.
But where does c++ fit in, say, in driver development?
OSs implement drivers as polymorphic entities. An OS is essentially a common
kernel that maintains an array of handles to drivers, and treats each one
with the same interface. That's why a Un*x, for example, exposes those
handles in its /dev folder.

C++ handles polymorphism very nicely, as classes, and OSs typically don't
use that system. They use C's system of pointers to functions. Each driver
comes with a block of pointers, and the interface is all the functions.

Because C++ can easily compile modules compatible with C,
I've always saw
people saying c++'s low level abilities ( or C ) on the internet, but I
have no idea how pointer is a low level tool ( other than modifying a
block of memory if wanted)
You wrote binary search trees, right?
About manipulating memory with pointers,
doen't OS shield one app from another when app launches( in protected
mode flat model)? than how is pointer useful in that way? through the
use of OS API?

The OS typically recognizes modules loaded at a certain time, or loaded from
certain regions, or something. It recognizes them as kernel modules, and
allows them to pass such pointers into special functions that convert them
into special OS-level pointers. These can then reach across module
boundaries.

Further speculation belongs on a kernel newsgroup, but because C++ can do
anything C can, it will work fine in the kernel. Most drivers are old, and
come from old code lineages, so they use C, but that's the only reason.

--
Phlip
http://c2.com/cgi/wiki?ZeekLand <-- NOT a blog!!!

[Your Uncle]

"Phlip" <ph******@yahoo.com> wrote in message
news:cn*******************@newssvr11.news.prodigy. com...

chy1013m1 wrote:

so far i've learned from various sources about c++'s high level
abilities

Oh, like STL, parsing, locales, etc.?

such as how to use c++ to solve topcoder problems, write a
binary search tree, pointers, stacks queues.etcetc.

Those are low level. Feel free to learn them, but on a job use them
sparingly. Go to STL first.

I knew that was one of the OP's mistakes, but I didn't see a constructive
way to point it out.

But where does c++ fit in, say, in driver development?

OSs implement drivers as polymorphic entities. An OS is essentially a
common kernel that maintains an array of handles to drivers, and treats
each one with the same interface. That's why a Un*x, for example, exposes
those handles in its /dev folder.

C++ handles polymorphism very nicely, as classes, and OSs typically don't
use that system. They use C's system of pointers to functions. Each driver
comes with a block of pointers, and the interface is all the functions.

Because C++ can easily compile modules compatible with C,

Interesting statements here. Must the non-c++ module have paid any
attention to, say, typedefs?

I've always saw
people saying c++'s low level abilities ( or C ) on the internet, but I
have no idea how pointer is a low level tool ( other than modifying a
block of memory if wanted)

You wrote binary search trees, right?

About manipulating memory with pointers,
doen't OS shield one app from another when app launches( in protected
mode flat model)? than how is pointer useful in that way? through the
use of OS API?

The OS typically recognizes modules loaded at a certain time, or loaded
from certain regions, or something. It recognizes them as kernel modules,
and allows them to pass such pointers into special functions that convert
them into special OS-level pointers. These can then reach across module
boundaries.

Further speculation belongs on a kernel newsgroup, but because C++ can do
anything C can, it will work fine in the kernel. Most drivers are old, and
come from old code lineages, so they use C, but that's the only reason.

The reason for it "still" being C is then that it hasn't broken yet and can
be manipulated by c++? cheers, f