Re:Windows 10 Technical Preview Source Tree
by aionescu on Wednesday December 31, 2014 @04:19PM
(#8821136)
Indeed, static libs caused massive duplication and not-always-correct source location in my script. Nice catch :)
Re:Windows 10 Technical Preview Source Tree
by DominikD on Thursday December 25, 2014 @12:07PM
(#8796635)
C++ code in kernel typically wouldn't fly for the new stuff, but I bet there were some legacy pieces, sure. But even then nothrow would be forced on new and prefast/prefix warnings around failed allocations would have to be handled.
Re:Windows 10 Technical Preview Source Tree
by asveikau on Thursday December 25, 2014 @12:14PM
(#8796650)
This is true. The driver I am thinking of didn't use C++ exceptions. I just found it weird not to use the pool APIs like everything else.
But speaking of exceptions the kernel did use a lot of SEH.
As for this directory tree... I found it creepy, like maybe source was leaked. The only inaccuracies I found relative to my memory of parts that I worked on was (1) I don't think they have done well tracking files that are part of static libraries and (2) what I presume are new files introduced by folks who came after me.