Conceptual Patch - Handle wrapper class

Hello Stefan,

After you commit patch I sent you (r20974), I checked if there are other
places with similar issues. I found out that wrapping class may help
here. It adds some overhead but not much. Some optimization can be still
done by trade it for readability and maintainability.

This is conceptual patch and is not intended as patch to be commit as is
(especialy for may English (better to say English like language :) )). I
don't have VC so I did not try to even compile it.
If you are not interesting about this in TSVN no problem, just let me know.

If you interest in it. There may be answers which may help to improve it.
Is there any situation when 0 is valid handler ?
   If no: would be better to use NULL (0) as Invalid handler.
   It may simplify test for invalid handle a bit, also bValid attribute
may be removed from class.
   As I understand INVALID_HANDLER_VALUE is for compatibily with win16 API.
Is there any situation when INVALID_HANDLER_VALUE is valid handler?
  if both are no: we don't need to pass invalid value into object
Is there any real bed efect when we call CloseHanlde with 0 or
INVALID_HANDLER_VALUE? As I understand INVALID_HANDLER_VALUE is also
pseudo handler to windows itself, or something like that.

-- 
Oto BREZINA, Printflow s.r.o., EU
<3D%22skype:tomas.blaho?call%22><3D%22skype:tomas.blaho?call%22>
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2710911
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].