Driver Problems? Questions? Issues?
Put OSR's experience to work for you! Contact us for assistance with:
  • Creating the right design for your requirements
  • Reviewing your existing driver code
  • Analyzing driver reliability/performance issues
  • Custom training mixed with consulting and focused directly on your specific areas of interest/concern.
Check us out. OSR, the Windows driver experts.

OSR Seminars


Go Back   OSR Online Lists > ntdev
Welcome, Guest
You must login to post to this list
  Message 1 of 1  
09 Jul 18 13:55
Tim Roberts
xxxxxx@probo.com
Join Date: 28 Jan 2005
Posts To This List: 12008
Re: RE: RE: RE: Re: [BULK] Re: Modern C++ Features in Kernel Mode Drivers

xxxxx@hotmail.com wrote: >> But with judicious appropriate comments, all should be well, and your chances >> of leaving the function's scope without releasing the lock are zero. > True, but consider the scenario when you may have to release the lock and subsequently re-acquire it in some cases. Ooh, that's so hard.  std::unique_lock supplies unlock() and lock() primitives, but it provides the very convenient guarantee that any lock will be released when it goes out of scope. > Apparently, you must be able to find a workaround by messing around with scopes and loops, but imagine how ugly it is going to look. Honestly, I don't know why you feel empowered to criticize tools you don't use and don't understand.  You are certainly not required to use C++ in your drivers, but you are entirely out of line to argue that C++ is inherently inferior.  It is provably not so. -- Tim Roberts, xxxxx@probo.com Providenza & Boekelheide, Inc.
Posting Rules  
You may not post new threads
You may not post replies
You may not post attachments
You must login to OSR Online AND be a member of the ntdev list to be able to post.

All times are GMT -5. The time now is 19:24.


Copyright ©2015, OSR Open Systems Resources, Inc.
Based on vBulletin Copyright ©2000 - 2005, Jelsoft Enterprises Ltd.
Modified under license