Note: This license has changed considerably from previous releases. Before purchasing or upgrading (even for free) to the 2.5 source, you should read this license carefully. In 2.5, the Interpreter front-end source code is Public Domain. The Interpreter back-end source can be purchased. Some parts of the back-end that were previously omitted are now included, but you are more restricted than before in your ability to distribute executables that you build with the source.

In exchange for payment, RDS will provide you with Euphoria and C source code that can be used to build a version of the RDS Euphoria Interpreter, using any of 7 supported C compilers on 4 platforms. Also included are batch files that perform all the required steps to build the Interpreter executable file on each platform. The only difference between what you can build, and the official RDS Interpreter, is the functionality that lets the official RDS interpreter decode legacy shrouded code created by the pre-2.5 shrouder. To protect the security of old shrouded programs and libraries, RDS is not releasing that decoder.

We have tested the source with 7 different C compilers, and we are satisfied that it can be compiled and linked correctly with all 7. However, we can't guarantee that you will be able to compile or link the source, or achieve the same level of speed and reliability. If you have trouble, we will provide you with some assistance during a 3 month technical support period.

The following restrictions will apply.

1. Copying the Source Files

You are permitted to make backup copies of the source files for your own use. In general, you may not distribute original or modified copies of any C file contained in this source code, and you may not distribute original or modified copies of any Euphoria file unless it happens to be identical to a file in the Public Domain source. Note that the interpreter back-end C files and some of the front-end Euphoria files are different from what is contained in the Public Domain (100% Euphoria) source. There are two exceptions to this general rule. (1) You can distribute any of these source files, possibly with your modifications, to RDS, and (2) you can distribute these possibly modified files to people who you know have purchased this version of the source. Contact RDS if you are in doubt about whether someone has purchased the source. If multiple programmers, either as individuals or in a company, wish to study or work together on the source, they must each pay RDS for a copy.

2. Distributing Executable Files And Libraries

You are permitted to build executables from this source. The batch files we provide let you build an interpreter executable for each platform and supported C compiler. It may also be possible for you to construct static and shared libraries. When we talk about "executable" files, we mean libraries as well.

Your ability to distribute executable files built using this source is limited. On the platforms that we currently support: DOS, Windows, Linux and FreeBSD, you may only distribute executables to RDS, or to others who are registered users of the 2.5 source. If you have developed a version of Euphoria for a client or customer, they must also purchase the interpreter source from RDS. On other platforms, you can distribute executables to anyone, either for free or a price, provided those executables do not also run on any platform supported by RDS. In other words, we encourage you to port Euphoria to new platforms.

If you submit an executable to RDS, and we consider it acceptable, we may choose to post it on our Web site for all users to benefit from. We will likely refuse executables that contain features that could cause forking of the Euphoria language, or fragmentation of the Euphoria community. We will also refuse executables that might reduce the demand for our products (Binder, Translator, Interpreter Source).

5. Ownership of New Features

You own the source code for any features or changes that you make, and you are not required to make public any source code that you develop. If you do make your source code public, other than to RDS, or those you are certain are entitled to this version of our source code, you must not expose lines of RDS source code along with it. The fact that you implemented a feature does not preclude RDS or anyone else from implementing the same or similar features.

6. Public Discussion

You can publicly discuss the algorithms used by our source code in open forums, and you can mention the names of C routines, variables and other identifiers in the code, but you must not reveal actual lines of source code.

7. Acknowledgement

You are required to acknowledge the use of our source code, list our Web site, http://www.RapidEuphoria.com, and indicate the general nature of any changes you made to our source code, in any derived programs that you distribute. The acknowledgement could be displayed by the program, or be in the accompanying documentation, but it must be plainly visible to most users.

8. Damages

RDS is not responsible to you for any damages that arise from your use of this source code, and you must inform your users, in your documentation or in your derived programs, that RDS is not responsible to them for any damages.

9. Evil Intent

You may not use the source to create any viruses, worms, trojans or other software that is intended to cause damage to any computer systems or networks, or that would intentionally harm the reputation of Euphoria or RDS.