Rule of thumb for naming wrapper classes -
I feel myself creating a significant number of shelter classes, purely because I
< / P> Ul> DirectoryInfo
or WindowsIdentity
) Then I would call myself 'W' (to indicate that this is a cover) and so I DirectoryInfoW
( DirectoryInfoWrapper NativeMethods.DuplicateTokenW
.
What will be the good rule of thumb after the naming of thumb squares?
Naming conventions Whatever work you do for the team you are working with. As long as everyone is right with a particular conference, then it is fine.
I prefer more verbose version, however, that is, DirectoryInfoWrapper
is understandable to anyone who is not familiar with the code. But this is just me.
Comments
Post a Comment