🚀 go-pugleaf

Yes, MS says don't use type identifiers, but they use them all the time. 
The simple fact is that when you are dealing with code items such as API
declarations  "Byval StrAbc$" takes up a lot less space than "ByVal StrAbc
as string".  When you have a list of six or seven parameters (not
uncommon), it stretches off the screen.  Readability suffers and 
consequently you get MORE errors from miscalls with wrong types rather than
less.  As for searching for StrAbc$...just don't.  Search for "StrAbc" and
you will get both "StrAbc" and "StrAbc$".  As a general rule, the only
place I would use the type identifiers is in the declaration.  They are
optional elsewhere (and are a pain to type).  Therefore, from an
operational standpoint, you still use var names with Str, Int, Lng, etc. 
and the only difference is in the dim statement.  NEVER rely on someone
typing abc$ to indicate a string.  The $ can be dropped without the
compiler complaining.

The bottom line is you shouldn't make a flat statement to not use type
declaration characters because MS says not to in a document, since they
violate their own naming rules whenever it's convenient for them. 

Chuck Bonner <chuck.bonner@stoneweb.com> wrote in article
<01bc7802$f03ba640$8510046f@vms2238>...
> Robert,

> However, according to  the <A
> HREF="http://www.microsoft.com/kb/articles/q110/2/64.htm">LONG Microsoft
> Consulting Services Naming Conventions for VB</A>, these type identifier
> suffixes are not recommended.
> 
> I can confirm from long experience in many development teams that they
are
> a nuisance.  For instance, if you want to find all references to a
variable
> and you highlight the declaration, "strName$," the search will not find
> places where the variable is referred to as "strName."  What is  the name
> of this variable?  Does it have a "$" in it or not?  The answer is, yes,
it
> has a "$" in it or not.
> 
> Do yourself and your colleagues a favor.  Don't use them.
> 
> -- 
> Chuck Bonner
> Stone & Webster Engineering Corp.
> Chuck.Bonner@stoneweb.com
> 
>