$NOPREFIX: Difference between revisions

From QB64 Phoenix Edition Wiki
Jump to navigation Jump to search
(Created page with "The $NOPREFIX metacommand allows all QB64 functions and statements to be used without the leading underscore (_). {{PageSyntax}} :$NOPREFIX {{PageDescription}} * QB64-specific keywords are by default prefixed with an underscore, in order to differentiate them from legacy keywords inherited from QBasic/QuickBASIC 4.5. * The convention exists in order to allow older code to be loaded and compiled in QB64 without naming conflicts with existing variables or const...")
 
No edit summary
Line 15: Line 15:




==Availability==
{{PageAvailability}}
* '''Version 1.4 and up'''.
* '''QB64 1.4 and up''' (QB64 Team)
* '''QBPE 0.5 and up''' (QB64 Phoenix Edition)





Revision as of 23:18, 29 April 2022

The $NOPREFIX metacommand allows all QB64 functions and statements to be used without the leading underscore (_).


Syntax

$NOPREFIX


Description

  • QB64-specific keywords are by default prefixed with an underscore, in order to differentiate them from legacy keywords inherited from QBasic/QuickBASIC 4.5.
  • The convention exists in order to allow older code to be loaded and compiled in QB64 without naming conflicts with existing variables or constants.
  • If you are writing new code with QB64, and not importing code from QBasic/QuickBASIC 4.5, $NOPREFIX allows you to reduce typing by not having to use underscores in modern keywords.
  • SUB _GL still must be prefixed.
  • When $NOPREFIX is used, QB64 keywords can be used both with or without the leading underscore, so that both _DISPLAY and DISPLAY are valid in the same program, for example.
  • $NOPREFIX must be the first line in a program.


Availability

  • QB64 1.4 and up (QB64 Team)
  • QBPE 0.5 and up (QB64 Phoenix Edition)


See also



Navigation:
Main Page with Articles and Tutorials
Keyword Reference - Alphabetical
Keyword Reference - By usage
Report a broken link