Click above to get retro games delivered to your door ever month!

 @
------------------------------------------------------------------------------
 Purpose:
 Specify the name of a script file.

 Syntax:
 @<scriptname>

 Description:
 Blinker supports nested script files of any size to a depth of 5 levels.
 The processing of nested script files is similar to a program function
 call: when Blinker encounters a nested script command, the current script
 file is suspended, the second script is processed, and then Blinker
 returns to the first script and resumes processing.

 When searching for a script, Blinker will first look in the current
 directory, and then in the path specified in the LIB environment variable.
 This will allow frequently used scripts which are rarely modified, (such as
 scripts for overlaying a particular library), to be stored in a common
 directory for convenience.

 Example:
 # Script file commands
 ...
 # Process the link script 'Myscript' here
 @Myscript
 # Continue with more script commands
 ...