🚀 go-pugleaf

; On 14 Jun 1997 00:14:32 GMT, "SCEA" <pmarshal@pacbell.net> wrote:

> 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. 
[snip!]

Do as I say and not as I do? <g>

Seriously though, just because MS does it doesn't make it right.
Right?

I personally hate to see these type declaration characters in code. If
the declare gets too long, use the line continuation character --
that's what it's for, after all.

The thing that really bugs me, though, is when using named arguments
when calling a sub or function. Stupid VB won't find a variable name
when doing a search and replace! For instance,

	Call SomeSub(Arg1:=var1, Arg2:=var2)

VB doesn't put spaces around the ":=", and if you try search and
replace to change "var1" into "string1" VB doesn't find it! This works
the same in VB4 or VB5.

Excuse the rant.


____________________
...Press any key to continue or any other key to quit
Dale Thompson
thompson01@sprynet.com