C++ RTL for NT kernel-mode drivers

Well kt133a, if you had just put this in the first post instead of buried deep in the thread:

"It hardly beleived this RTL can be considered as a part of some commercial
product in some future. Let’s just look at the current state of the project:

  1. this is entirely a private investigative initiative;
  2. a whole bunch of undocumented or poorly-observed or reverse-engineered
    technologies is used,
  3. the officially unsupporetd or unrecommended facilities are used,
  4. initially released with the intention to be of an interest to the enthusiast
    of the C++ using in the NT kernel environment.

I doubt anyone would have even bothered responding to the initial post if it said that. We’ve had various EH usage in the kernel since the Walter Oney days and this particular effort really isn’t going in the right direction. Maybe instead it would be better to contact the provider of the best EH library out there and work with them to bring it forward instead of trying to re-invent the wheel and coming up a little short. I recall from one EH library that stack usage is now a non-issue.

> To see the sort of discipline involved in Linux-type projects, take a

look at http://www.freebsd.org/releases/10.0R/schedule.html

FreeBSD is not Linux-type

FreeBSD is a cathedral

Linux is a bazaar

:slight_smile:


Maxim S. Shatskih
Microsoft MVP on File System And Storage
xxxxx@storagecraft.com
http://www.storagecraft.com

>do I have to BOTH mark the IRP pending *and* return STATUS_PENDING.

Rajeev Nagar had an excellent explanation of this in his FS book, circa 1998.


Maxim S. Shatskih
Microsoft MVP on File System And Storage
xxxxx@storagecraft.com
http://www.storagecraft.com

> I doubt anyone would have even bothered responding to the

initial post if it said that. We’ve had various EH usage
in the kernel since the Walter Oney days and this
particular effort really isn’t going in the right direction.
Maybe instead it would be better to contact the provider
of the best EH library out there and work with them to
bring it forward instead of trying to re-invent the
wheel and coming up a little short. I recall from one
EH library that stack usage is now a non-issue.

It seems to look not such a kind of pessimistic. The current library is modular enough internally for the EH-stuff to be quickly substituted by some more advanced implementation. On you courteousy you can post here some details about the lib mentioned, this is really interesting.

From my own little viewpoint, having code available to the
developers that is problematic and/or does not follow
best practices, is worse than having no code available.
This type of code is just a big hole for unsuspecting
devs to fall into.

This viewpoint IMO looks a bit like “let’s don’t give the forks to that barbarians for them not to prick out their eyes”. I lack this opinion but just can understand you may have solid argumentation for this e.g. similar as posted above the topic.

It’s hard enough to write Windows drivers without having
to deal with additional unknowns.

This is entirely the true. And in addition the c++ is a PL to be considered as a complex thing enough. But it hardly supposed the people involved in these activities are uncapable to see the pitfalls supplied.
So now when the most misconceptions (added mainly by me, because of it has became a bit unexpected that so many readers take this project as production ready) are probably cleared, can we lead to achieve the goals implicetly presumed as the starting reasons of this topic? Namely those goals are: to make the project available for most curious people as possible, to discuss the internal mechanics for the optimizations to get appeared and bugs to get disappered. It’s believed the project in spite of the well-known restrictions and admissions appears to be viable enough to be of interest for even if a bit of NT-kernel community besides me. -)

Oh BTW, thanks, Mr. Viscarola, the ‘who effectively said “better some software than no software”’ - now it’s me ;-).

> post here some details about the lib mentioned, this is really interesting.

Happy reading:

https://www.osronline.com/ShowThread.cfm?link=203234

> > post here some details about the lib mentioned…

Happy reading:
https://www.osronline.com/ShowThread.cfm?link=203234

Oh thanks, but i’d certainly got familiar with those earlier. And that efforts probably have remained unreleased as open-source by the current time for all archs besides ‘x86’, and attempts to get the author e-mail’ed are being currently unsuccessful. But it believed if the author finds the current projects interesting even if in some parts he can use it on his own.