“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
> Or not. Can you write drivers for NT today in VB (even VB.NET)? Or in
IA64
assembler language?
Well, I meant, from applicable tools of course.
/regards/
Stipulating for the moment that your assertion about C/C++ is correct, I
doubt that any but the most unusual driver would be doing anything that
could benefit from such features. Maybe a graphics driver could. That is
a class of driver with special needs.
–
If replying by e-mail, please remove “nospam.” from the address.
James Antognini