Programming Guide

Parent Previous Next

Programming Guide.

A SCRAMBLECODE program has this top-down structure:


At the top is your project. It defines all your properties for compilation etc.

Source files

The project can have multiple source files attached. They are simply text files with your source code.


Each source file can contain multiple classes.

Class members

Each class can have multiple fields and functions with public or private access.


Each function can have multiple parameters, variables and statements.

Programming in SCRAMBLECODE is all about writing classes and class-functions using types.

Types are grouped using two categories:

The detailed descriptions of types are done later in their respective sections due to the amount of information.

This programming guide however will focus on how to write functions and the code in them. Some source code examples will be presented for demonstration purposes. These examples will be using simple standard types as Integer, String, Boolean etc.

Writing Source Code.

SCRAMBLECODE is not case sensitive. You can write your source code using lowercase, uppercase, capitalization or whatever. The IDE has an option to present keywords and code on screen in different styles and coloring. It can be changed to your preference or switched off.

The raw text you write is the raw text which is saved in the source file - even if it looks different on the screen. Lets say you use the word function written and saved to a file in lowercase. This may be presented in the editor as either function or Function or FUNCTION. It all depends on the style options you have chosen.

Programmers Background.

SCRAMBLECODE is almost always used in combination with other programming languages. This means that you probably have a good deal of experience with the technical aspects of classes, functions, fields, variables, scope, public and private access, arguments, passing parameters by value or by reference and much more.

This programming guide expects that you have some knowledge about these issues. This assumption allows for a shorter and more concise presentation of each programming issue.