To use this website fully, you first need to accept the use of cookies. By agreeing to the use of cookies you consent to the use of functional cookies. For more information read this page.

Official ZPE Programming Environment documentationZPE Programming Environment documentation

The pages associated to this page cover the syntax of ZPE as well as some underlying development strategies and some of the key concepts. If you are using ZPE you should find this set of pages very useful.

Getting started

When you have download the ZPE Programming Environment executable you will need to know how to use it.


The following is a list of all the main features of the YASS language:

Language constructs

The following list is a list of all syntax and language constructs for YASS:

Object syntax documents

The following documentation covers objects built-in to the language itself and how they work as well as their exposed functions.

Predefined functions

The following is a concise list of all built-in functions and links to pages dedicated to them.

Please know that deprecation means that a function or structure has a planned removal date but still exists for backward compatibility sake. The function or structure becomes deprecated when the replacement feature is added and is scheduled for removal a few versions later from deprecation.

There are several things to note about these functions and how they appear on this website.

Firstly, the [ ] around some parameters refers to a parameter that is optional, i.e. a parameter that does not need to be defined to satisfy the call request on the function.

Secondly, if a function can take a parameter message1, as well as being able to take message2, message3 and messageN, then the function can take infinitely many parameters.

Finally, most of the functions have alternative names. This is simply an alias to the function and if necessary can be completely overwritten using the built-in function overwriting.

None of the Core Functions can be overwritten by any other function - this is a language design feature.

When a parameter or return type is mixed, it implies that it has multiple types and can be either overloaded or the program should expect any of a bunch of return types from this function. This should be handled by the programmer when assessing the value using the get_type function.

Old functions that have since been removed but still have documentation are available here.

Other documentation


There are no comments on this page.

New comment
Provide feedback on this page
Comments are sent via email to me.