Difference between revisions of "COMMON"

From QB64 Wiki
Jump to navigation Jump to search
imported>Clippy
m
imported>SMcNeill
m (-)
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
'''COMMON''' shares common variable values with other Linked or [[CHAIN]]ed modules.
+
[[COMMON]] shares common variable values with other linked or [[CHAIN]]ed modules.
  
 +
==Legacy support==
 +
* The multi-modular technique goes back to when QBasic and QuickBASIC had module size constraints. In QB64 [[COMMON]] has been implemented so that that older code can still be compiled, though '''it is advisable to use single modules for a single project (not counting [[$INCLUDE]] libraries), for ease of sharing and also because the module size constraints no longer exist.'''
  
::::::''Syntax:'' COMMON [SHARED] [/blockname/] variablelist
 
  
 +
{{PageSyntax}}
 +
: [[COMMON]] [SHARED] variableList
  
 +
 +
{{PageDescription}}
 
* COMMON must be called before any executable statements.
 
* COMMON must be called before any executable statements.
 
 
* [[SHARED]] makes the variables shared within [[SUB]] and [[FUNCTION]] procedures within that module.
 
* [[SHARED]] makes the variables shared within [[SUB]] and [[FUNCTION]] procedures within that module.
 +
* variableList is the list of common variables made available separated by commas.
 +
* Remember to keep the variable type ''order'' the same in all modules, as the variables names don't matter.
 +
* [[COMMON SHARED]] is most commonly used to share the variables with subs and functions of that module.
 +
* '''Note: Values assigned to shared variables used as procedure call parameters will not be passed to other procedures. The shared variable value must be assigned inside of the [[SUB]] or [[FUNCTION]] procedure to be passed.'''
  
* /blockname/ gives the ability to name a block of variables (ex. COMMON /thename/ a, b, c), this name can later be referenced in the module to only give access to those variables. As such many COMMON statements can be issued with different names to be shared in different modules.
 
 
* Variablelist is the list of common variables made available separated by commas.
 
 
* Remember to keep the variable type ''order'' the same in all modules as the variables names don't matter.
 
 
* [[COMMON SHARED]] is most commonly used (hence you almost always see them together in code), as then you don't need to share the variables separately in the module for use in subs and functions of that module.
 
 
* Common variables can only be passed by [[CHAIN]] using compiled modules if BRUN45.EXE is included with the program.
 
 
* Linked files are compiled first and linked with LINK.EXE in QB. '''QB64''' cannot link files presently!
 
 
 
 
 
''See:'' [[COMMON SHARED]], [[CHAIN]]
 
 
 
 
==Navigation:==
 
  
[[Keyword_Reference_-_Alphabetical|Go to Keyword Reference - Alphabetical]]
+
{{PageSeeAlso}}
 +
* [[COMMON SHARED]], [[CHAIN]]
 +
* [[DIM]], [[REDIM]], [[SHARED]]
 +
* [[DEFSTR]], [[DEFLNG]], [[DEFINT]], [[DEFSNG]], [[DEFDBL]]
  
[[Keyword Reference - By usage|Go to Keyword Reference - By usage]]
+
{{PageNavigation}}

Latest revision as of 14:31, 10 September 2017

COMMON shares common variable values with other linked or CHAINed modules.

Legacy support

  • The multi-modular technique goes back to when QBasic and QuickBASIC had module size constraints. In QB64 COMMON has been implemented so that that older code can still be compiled, though it is advisable to use single modules for a single project (not counting $INCLUDE libraries), for ease of sharing and also because the module size constraints no longer exist.


Syntax

COMMON [SHARED] variableList


Description

  • COMMON must be called before any executable statements.
  • SHARED makes the variables shared within SUB and FUNCTION procedures within that module.
  • variableList is the list of common variables made available separated by commas.
  • Remember to keep the variable type order the same in all modules, as the variables names don't matter.
  • COMMON SHARED is most commonly used to share the variables with subs and functions of that module.
  • Note: Values assigned to shared variables used as procedure call parameters will not be passed to other procedures. The shared variable value must be assigned inside of the SUB or FUNCTION procedure to be passed.


See also



Navigation:
Go to Keyword Reference - Alphabetical
Go to Keyword Reference - By usage
Go to Main WIKI Page