Re: C++ in kernel. was Re: Batch file for Visual Stud io build,

Guys, I advocate using anything that gets the job done. From assembler to
Lisp. But some languages and tools get the job done faster.

Alberto.

-----Original Message-----
From: Mark Roddy [mailto:xxxxx@hollistech.com]
Sent: Monday, October 21, 2002 4:03 PM
To: NT Developers Interest List
Subject: [ntdev] Re: C++ in kernel. was Re: Batch file for Visual Stud
io build,

Actually the odd part of these two eternal threads is that Alberto, who
apparently is older than snot, and even perhaps older than me, is a
staunch advocate of writing drivers that never use any defined OS
interfaces and always descend into platform specific hackery, while at
the same time espousing the use of c++ OOPS etc. I guess he is
advocating OOH, that is Object Oriented Hackery, using C++ :slight_smile:

Besides Gary has me on the wrong side of the C(blech!) vs C++ (yeah!)
idiocy.

[Warning, topic shift]

Finally I thought Gary’s suggestion that eliyas provide a virtual scsi
miniport sample was a bit over the top.

===========================
Mark Roddy
Consultant, Microsoft DDK MVP
Hollis Technology Solutions
xxxxx@hollistech.com
www.hollistech.com
603-321-1032

-----Original Message-----
From: “Moreira, Alberto”
To: “NT Developers Interest List”
Date: Mon, 21 Oct 2002 12:57:22 -0400
Subject: [ntdev] Re: C++ in kernel. was Re: Batch file for Visual Stud
io build,

> Gary, I predate C. Before Kernighan and Ritchie, before Burroughs
> Algol,
> what language do you think we old farts used to write operating systems
> ?
> And actually, the last driver I wrote for Win9x, not that long ago, was
> written in Assembler.
>
> Alberto.
>
>
> -----Original Message-----
> From: Gary G. Little [mailto:xxxxx@inland.net]
> Sent: Monday, October 21, 2002 12:39 PM
> To: NT Developers Interest List
> Subject: [ntdev] Re: C++ in kernel. was Re: Batch file for Visual Stud
> io build,
>
>
> Brag brag brag … and if I state that I have directly written
> in
> machine language (ya know … that stuff that all assemblers out put)
> … I
> guess I would have you beat. I have done that by the way. It’s not
> enjoyable, and I do have much more better things to do with my time,
> like
> swimming with my grandkids, but I can do that mundane task when
> required.Really big whoop.
>
> I can see that there are two never ending threads in these groups …
>
> One is the Eternal tale of Princess C being devoured by the Obseqious
> Ogre
> of OOPS. Hmmm in that one the evil wizard Alberto flings brazen bolts
> of
> obfuscation against the pitifal palace of C while Sir Roddy, Sir
> Shatski,
> and other white knights of C-dumb utilize the “force” to deflect these
> phlaming phlatulants.
>
> The second has mostly the same characters … Evil Alberto, Sir Roddy
> and
> Sir Shatski. Hmmm really its the same story line … but instead of
> Princess
> C in the palace of C, it’s his highness Kernel OS in the Fortress of
> HAL.
>
> oohhhh this is getting silly …
>
> –
> Gary G. Little
> Have Computer, Will Travel …
> 909-698-3191
> 909-551-2105
>
> “Moreira, Alberto” wrote in message
> news:xxxxx@ntdev…
> >
> > Well, this kernel dev has actually developed drivers in assembler,
> and let
> > me tell you, sometimes I prefer it over C.
> >
> > Alberto.
> >
> >
> > -----Original Message-----
> > From: Peter Viscarola [mailto:xxxxx@osr.com]
> > Sent: Sunday, October 20, 2002 7:45 PM
> > To: NT Developers Interest List
> > Subject: [ntdev] Re: C++ in kernel. was Re: Batch file for Visual
> Studio
> > build,
> >
> >
> > “Andrew Sloven” wrote in message
> > news:xxxxx@ntdev…
> > >
> > > It’s up to programmer to decide under which
> > > circumstances to use certain language.
> > >
> >
> > Or not. Can you write drivers for NT today in VB (even VB.NET)? Or
> in
> IA64
> > assembler language?
> >
> > Well, you COULD do these things but the effort required makes them
> > impractical, at the very least. So, at least at face value your
> statement
> > isn’t valid.
> >
> > But aside from that: I just hope whoever winds up with a driver that
> you
> > decided to write in C++ has the same capability at maintaining it,
> changing
> > it, and re-working it that you would have.
> >
> > You see, it’s not really about YOU… it’s about everybody ELSE.
> >
> > When I write code, I realize that I’m likely not the last person to
> touch
> > it. It’ll be tweaked, prodded, and poked by all sorts of engineers
> – who
> > will range in talent from supremely competent to utter moron.
> >
> > So, just as I carefully choose what syntax to use to express a
> concept (to
> > ensure utmost clarity for those who come after me), one must do
> likewise
> > when choosing a language.
> >
> > Peter
> > OSR
> >
> >
> >
> > —
> > You are currently subscribed to ntdev as:
> xxxxx@compuware.com
> > To unsubscribe send a blank email to %%email.unsub%%
> >
> >
> >
> > The contents of this e-mail are intended for the named addressee
> only. It
> > contains information that may be confidential. Unless you are the
> named
> > addressee or an authorized designee, you may not copy or use it, or
> disclose
> > it to anyone else. If you received it in error please notify us
> immediately
> > and then destroy it.
> >
> >
> >
> >
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@compuware.com
> To unsubscribe send a blank email to %%email.unsub%%
>
>
>
> The contents of this e-mail are intended for the named addressee only.
> It
> contains information that may be confidential. Unless you are the named
> addressee or an authorized designee, you may not copy or use it, or
> disclose
> it to anyone else. If you received it in error please notify us
> immediately
> and then destroy it.
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@hollistech.com
> To unsubscribe send a blank email to %%email.unsub%%


You are currently subscribed to ntdev as: xxxxx@compuware.com
To unsubscribe send a blank email to %%email.unsub%%

The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.