Available on: all targets

CONFIGURE

The CONFIGURE command allow to customize hardware configuration, and gives the possibility of generating hardware selection menus via software. The configuration allows two types of manipulation: a STATIC one, which is adopted at compilation time (useful for development and unconventional startup) and a DYNAMIC one, which is adopted at execution time (useful for creating configuration menus). Static changes must begin with the CONFIGURE STATIC keywords, while dynamic changes must begin with the CONFIGURE DYNAMIC keywords. By default, the changes are to be considered static.

Each hardware change request must begin with the CONFIGURE keyword followed by the name of the hardware to be configured. Each request for hardware modification must concern one or more parameters prefixed by the SET command. The value that can be assigned to these variables must be consistent with the expected and acceptable values.

Finally, it is possbile to assign multiple values consecutively, separating them with a comma, without using the SET command.

syntax example abbreviation back to keywords

SYNTAX

 CONFIGURE STATIC hw SET p1 = v1 [, p2 = v2 [, ...]]
 CONFIGURE DYNAMIC hw SET p1 = v1 [, p2 = v2 [, ...]]


Legend
  • id : identifier
  • type : datatype
  • v : value
  • "..." : string
  • [...] : optional

ABBREVIATION: Cfg

Join BASIC 10Liner Contest with ugBASIC!

An interesting competition is held at the beginning of each year: the BASIC 10Liner Contest. It is possible to use ugBASIC to participate in the next "BASIC10Liner" competition, in the following categories:

  • PUR-120 - A game in 10 lines of max 120 characters (w/abbrev.)
  • EXTREME-256 - A game in 10 lines of max 256 characters (w/abbrev.)
  • SCHAU - Any program in 10 lines of max 256 characters (w/abbrev.)
In order to reduce space you can use this abbreviation for this instruction: 

CONFIGURE ↔ Cfg

Any problem?

If you have found a problem with this keyword, if you think there is a bug or, more simply, you would like it to be improved, open an issue for this example on GitHub.
Thank you!

open an issue BACK TO KEYWORDS