The Weird and The Wonderful

Bigdeak wrote:

Yes, this confirms my oppinion. VB6 is the language with the most chaotic code i have ever seen. It's really a language for small short-life stuff.
For those who never where in that situation:
Imagine if you have a project with code like this in this language, but with 100000 source code lines...

With Object.Its.So.Nested


(...)


  abc = .Some.Property // WTF?


(...)

End With

Jacek Gajek wrote:

1. Option Explicit Off

Jacek Gajek wrote:

2. On Error Goto Label37

Dim a As Integer = "1"

Dim c As Object

Select Case c
    Case 1
        ' do something 1
    Case "horror"
        ' its really bad
    Case Color.Green
        ' its even worst
End Select

OriginalGriff wrote:

No, it doesn't! Try with an empty catch would only work the same if you surrounded each and every single line of code with it's own, independent, try...empty catch block. Not even the laziest programmer on the planet would do that...

Richard A. Dalton wrote:

All you need is a try with an empty catch above the top level code, e.g. in a Button Click event, and all lower level code is covered.

On error resume next
x = 3
x = x / 0
x = x + 1

try
   {
   x = 3;
   x = x / 0;
   x = x + 1;
   }
catch {}

try { x = 3; } catch{}
try { x = x / 0; } catch{}
try { x = x + 1; } catch{}

OriginalGriff wrote:

It's not the same: On Error Resume Next causes execution to continue from the statement after the one that cased the error. An empty catch block will continue from the statement following the catch.

Dim a As Variant
a = long_expression_possibly_returning_null
If a = True Then
some_code
Else
more_code
End If

Dim a As Variant
a = long_expression_possibly_returning_null
If a = True Then
some_code
ElseIf a = False Then
more_code
End If