• How to declare and initialize a variable,
• How to access the properties of a variable,
• The rules for variable scope.

Declaring a variable

Declaring a variable and inializing it

Declaring several variables

Detailed syntaxes

• The a and an keywords are optional: they provide better readability.
• When several variables of the same type are declared and initialized on the same line, only the last variable is initialized.
  To declare and initialize several variables at the same time, use the multiple initialization.
• It is forbidden to use several variables with the same name in an event/process (regardless of the type of these variables).

Examples

• Declaring simple variables:
  
  NomClient is string
  Compteur is int
  Prix is real
  i,j,k are int
  
  
  The type inference allows you to use the following syntaxes:
  
  let Montant = 1500.69 // type réel
  let Ville = "Montpellier" // type chaîne
  
• Declaration of an Variable type Border:
  
  MonCadre is Border
  

Critical section" attribute

When declaring a variable, this variable can be associated with a critical section by using the critical section attribute.

The syntax is as follows:

VariableName is VariableType <critical section>

or

VariableName is VariableType, critical section

The code sections that use these variables must be found between CriticalSectionStart and CriticalSectionEnd.

Special case: A critical section is automatically associated with the variables on which simple operations are performed, such as:

• assigning a value.
• retrieving a value.
• incrementat, decrement (+, -, ++, --, +=, -= operators +, -, ++, --, += -=).

Example:

// Global declarations of WIN_STAT window
gcySum is currency, critical section
gcyMax is currency, critical section
...

// Code run by several threads
cyOrderAmount is currency 
...
// atomic operation, the critical section is automatically managed by WLanguage
gcySum += cyAmountOrder

// multiple operation, it is necessary to implement the critical section explicitly
utiliser CriticalSection(gcyMax) IN
	IF cyAmountOrder > gcyMax THEN
		gcyMax = cyAmountOrder
	END
END

Remarks:

• The critical section attribute is allowed for:
  • the global project variables, set of procedures, window, page and report.
  • the local variables.
  • the members of classes.
  • the arrays: in this case, the attribute is associated with the array and not with the array elements.
• The queues and the stacks are protected by default: the critical section attribute is not required.

Not available in Android and in Android widget.

Syntaxes

• Assigning a property of the variable:
  
  <Nom de la variable>.<Propriété> = <Valeur>
• Reading a property of the variable:
  
  <Nom de la variable>.<Propriété>

Example

Rule

• If a variable "global" to the project and a variable "global" to a window have the same name:
  • the variable "global" to the window will be used in all the events or processes of the window and window controls as well as in its "local" procedures.
  • the variable "global" to the project will be used in all the other processes.
• If a variable "global" to the project and a variable "local" to a process have the same name:
  • the "local" variable will only be used in the process where this variable was declared.
  • the variable "global" to the project will be used in all the other processes.
• If a variable "global" to a window and a variable "local" to a process of this window have the same name:
  • the "local" variable will only be used in the process where this variable was declared.
  • the variable "global" to the window will be used in all other events or processes of the window and its controls (as well as in its "local" procedures).
  • none of these two variables can be used in the rest of the project.

Exception

Special case: Reports & Queries

• The variables global to the project can be used in the reports and queries created and/or modified in "Reports & Queries".
• The items for which "Visible to the end user in "Reports and Queries"" is checked in the data model editor can be used in Reports and Queries. If this option is unchecked, the field can only be used indirectly (the user does not have the option of completing the field, and the field is not available in Wizards, description windows, etc.).

Name conflict: ambiguous use of a type