PRB: Non-Reserved Word w/ Colon Behaves Differently in VB 4.0 (129935)
The information in this article applies to:
- Microsoft Visual Basic Standard Edition, 32-bit, for Windows 4.0
- Microsoft Visual Basic Professional Edition, 16-bit, for Windows 4.0
- Microsoft Visual Basic Professional Edition, 32-bit, for Windows 4.0
- Microsoft Visual Basic Enterprise Edition, 16-bit, for Windows 4.0
- Microsoft Visual Basic Enterprise Edition, 32-bit, for Windows 4.0
This article was previously published under Q129935 SYMPTOMS
Using Non-reserved keywords followed by a colon may produce different
results in Visual Basic version 4.0.
A reserved keyword in Visual Basic cannot be used as the name of a
user-defined function. However, a non-reserved keyword may be used as the
name of a user-defined function.
In Visual Basic version 4.0 a non-reserved word followed by a colon is
interpreted as a line label. Previous versions of Visual Basic checked to
see if this is a statement followed by another statement on the same line.
Similar behavior occurs when you use a user-defined subroutine with no
parameters followed by a colon and another statement.
RESOLUTION
To avoid the confusion that this could potentially cause, Microsoft
recommends that you use colons only for line labels. Write each individual
statement on a separate line. Not only does this allow you to avoid
confusion, it also makes your code easier to read.
STATUS
This behavior is by design.
Modification Type: | Major | Last Reviewed: | 12/9/2003 |
---|
Keywords: | kbprb KB129935 |
---|
|