Android Question Class_Globals vs Initialize

[Alessandro71]

A variable initialization in a Class_Globals gets executed when Initialize is called.
What is the difference between initializing variables in Class_Globals vs in Initialize?

Sub Class_Globals
    Private test as boolean = true
End Sub

 

[LucaMs]

A variable initialization in a Class_Globals gets executed when Initialize is called.

If so, it should be the same, but...

Since I have:
Sub Class_Globals
and
Sub Initialize

WHY NOT initialize EVERYTHING in the Initialize?
I can mix a fruit salad in the bathroom (Class_Globals), but why not in the kitchen (Sub Initialize)?!

Why complicate your life when it's already complicated enough?

 

[Alessandro71]

Maybe there's a use case we aren't aware of.
And that's what I'm asking for.

 

[Daestrum]

Possibly the logic that in Class_Globals you set the value that you want it to start with, irrespective of who creates it. Whereas in Initialize, it sets the value to what the caller wants (like a name or address field).

 

[Alessandro71]

Possibly the logic that in Class_Globals you set the value that you want it to start with, irrespective of who creates it. Whereas in Initialize, it sets the value to what the caller wants (like a name or address field).

that's a valid use case: Initialize can have parameters, while Class_Globals is static

 

[stevel05]

There is a difference between assigning a value to a variable and initializing a variable. The Globals subs (class or otherwise) should only be used for simple assignments, where as in the initialize sub, you can do more complex assignments and initializations:

Sub Class_Globals
    Private test As Boolean = True
    Private Count As Int = 0
    Private MaxCount As Int
    Private MyList As List
End Sub

Sub Initialize
    MyList.Initialize
    MyList.AddAll(Array As String("First", "Second"))
    MaxCount = CountElements

End Sub

Sub CountElements As Int
    Return MyList.Size
End Sub

An over simplified example.