Revision [16673]

This is an old revision of KeyPgStatic made by FxMwikki on 2013-03-23 11:48:05.

 

STATIC


Defines variables, objects and arrays having static storage

Syntax:
Static symbol [ ( [ subscripts ] ) ] [ KeyPgAs as DataType DataType ] [ , ... ]
or
{ KeyPgSub sub|KeyPgFunction function } proc_header Static
[ ... ]
KeyPgEndblock end { KeyPgSub sub|KeyPgFunction function }
or
{ KeyPgType Type | KeyPgClass Class } typename
Static symbol [ ( [ subscripts ] ) ] [ KeyPgAs as DataType DataType ] [ , ... ]
...
End { KeyPgType Type | KeyPgClass Class }
KeyPgDim Dim typename.symbol [ ( [ subscripts ] ) ] [ KeyPgAs as DataType DataType ] [ , ... ]

Parameters:
symbol
variable or array symbol name.
subscripts
a comma-separated list of subscript ranges.
proc_header
procedure header for a procedure definition.

Description:
Specifies ProPgStorageClasses static storage for variables, objects and arrays; they are allocated at program startup and deallocated upon exit. Objects are constructed once when they are defined, and destructed upon program exit.
When declaring static arrays, only ProPgLiterals numeric literals, KeyPgConst constants or KeyPgEnum enumerations may be used as subscript range values. Static variable-length arrays must be declared empty (no subscript range list) and resized using KeyPgRedim Redim before used.
In both iterative and recursive blocks, like looping CatPgControlFlow control flow statements or procedures, static variables, objects and arrays local to the block are guaranteed to occupy the same storage across all instantiations of the block. For example, procedures that call themselves - either directly or indirectly - share the same instances of their local static variables.
A static variable may only be initialised with a constant value: its starting value is set at the start of the program before any code is run, and so it cannot depend on any variables or functions in it.
When used with module-level and member procedure declarations, Static specifies ProPgStorageClasses static storage for all local variables, objects and arrays.
At module-level variable declaration only, the modifier KeyPgShared Shared may be used with the keyword Static to make module-level static variables visible inside procedures.
When used with UDT, each Static member variable needs an additional declaration. The declaration inside the UDT is the prototype that is visible to every module seeing the UDT declaration (like with methods). The second declaration (outside the UDT), only needed once in the whole program, allocates and optionally initializes the static variable.
A Static member variable is visible throughout the entire program (inside any procedure) even if the modifier KeyPgShared Shared is not specified in the second declaration (Static and KeyPgShared Shared are useless in the second declaration). So, Static member variables can be called directly anywhere in code, or on objects of type typename.
KeyPgStaticMember Static (Member) is also used in member procedure declarations to specify static member procedures.

Examples:
Sub f
    '' static variables are initialized to 0 by default
    Static i As Integer
    i += 1
    Print "Number of times called: " & i
End Sub

'' the static variable in f() retains its value between
'' multiple procedure calls.
f()
f()
Will output:

Number of times called: 1
Number of times called: 2


'Assign an unique ID to every instance of a Type (ID incremented in order of creation)

Type UDT
  Public:
    Declare Property getID () As Integer
    Declare Constructor ()
  Private:
    Dim As Integer ID
    Static As Integer countID
End Type
Dim As Integer UDT.countID = 0

Property UDT.getID () As Integer
  Property = This.ID
End Property

Constructor UDT ()
  UDT.countID += 1
  This.ID = UDT.countID
End Constructor


Dim As UDT uFirst
Dim As UDT uSecond
Dim As UDT uThird

Print uFirst.getID
Print uSecond.getID
Print uThird.getID


Differences from QB:
See also:
Back to Procedures
Back to Variable Declarations
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki



sf.net phatcode