The Script Programming Language/Files

From SCI Wiki
Jump to: navigation, search

The Original SCI Documentation

Chapter: 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | Index

The Script Programming Language


Author: Jeff Stephenson



Source files for the script compiler have the extension .sc, header (include) files have the extension .sh. Source files may have any filename -- and are two examples. The output file from the compilation will have the name script.nnn where nnn is determined from the script# command (covered below) which is present in the file.

There are six files besides the source file and any user-defined header files which are involved in a compilation.


This file contains the information about the structure of the classes which have been defined in the application. It is read automatically by the compiler and is rewritten by the compiler after a successful compilation in order to keep it up to date. The user need not be concerned with it.


This contains definitions of selectors which are used in object-oriented programming. It is automatically included in a compile and, like classdef, is rewritten after a successful compile. Any symbol in a properties or methods statement or in the selector position in a send to an object is assumed to be a selector and is assigned a selector number in included in selector.

This contains the definitions for interfacing with the kernel (the machine language interpreter). It is maintained by the kernel programmers and is automatically included in

This contains the definitions for interfacing with the various system classes. It is initially provided by the kernel programmers. If you wish to tweak the system scripts yourself, you will also be responsible for maintaining your copy of It should be included in all compiles.


This is the compiled output of vocab.txt, generated by the vocabulary compiler vc. It is automatically included in a compile.


This is an output file of the compiler which is used by the kernel to determine which script a given class is defined in. You needn't do anything to it other than not delete it.

There are two sc commands for dealing with source code organization:


The script# command sets the script number of the output file:

(script# 4)

sets the output file name to script.004, regardless of the actual name of the source file.


This includes a header file in the current source file at the current position.

(include "/sc/")


(include /sc/

include the file /sc/ Include files may be nested as deeply as desired.

When including a file, the compiler first looks for the file in the current directory. If it fails to find it there, it then looks for it in the directories specified in the environment variable SINCLUDE. This variable is just like the DOS PATH variable -- the directories to search are separated by semi-colons. Thus, if you want the compiler to look for include files in f:/games/sci/system and c:/include if it doesn't find them in the current directory, you put the line

set sinclude=f:\games\sci\system;c\include

in your autoexec.bat file.




Table of Contents


< Previous: IntroductionNext: Definitions >