> The WDK is using standard library files that are older than some people
here. What is preventing getting these updated to the latest file set? The
language has marched a long way since the 90’s. No one is asking for
exceptions and i/o. But certainly std::byte, std::array, std::unique_ptr,
and others would be terrific to have in the kernel arsenal. The key here is
to allow use of standard things (std: that are well documented and
understood by developers, not proprietary wil:: things copy and pasted from
std:: concepts. And the foundation of any higher level c++ library should be
built on std:: building blocks.
Hmmm. IMO, anything that allocates/deallocates behind the scenes would
be a bad bad bad, very bad idea in the kernel.
It would take a lot of time for some (as old as myself :)) to not
think about those, but newbies will certainly run at it. And unplanned
allocations/reallocations are a bad bad bad bad thing here I know -
I crashed servers becuase of it, when I started (for not using
lookasides).
std:array/list/map and even unique_ptr sound exactly like the kind of
stuff that would be the problem, without the user realizing it,
without considerable previous experience.
My 5c on this matter. I love the wrappers around kernel
primitives/structures though.