- Iris specification
Iris is a collection of domain-specific programming languages together with a systems programming language.
Iris is focused at high-performance and reliability, along with a simple and elegant syntax.
Unlike many other programming languages trying to become the "C++ killers", our aim is driven around providing useful & innovative features, and building a language that remains active and used for the years to come.
All the sets of characters defined at this section are conforming the UTF-8 encoding.
One of the following UCS domains:
U+0009-U+000A or U+0020
or one of the following UCS character descriptions:
Horizontal tabulation
Line feed
Space
One of the following glyph representations of UCS characters:
_, A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, W, X, Y, Z, a, b, c, d, e, f, g, h, i, j, k, l, m, n, o, p, q, r, s, t, u, v, w, x, y, z
or one of the following UCS domains:
U+0041 - U+005A, U+0061 - U+007A or U+005F
One of the following glyph representations of UCS characters:
0, 1, 2, 3, 4, 5, 6, 7, 8, 9
or one of the following UCS domains:
U+0030 - U+0039
One character of the alpha characters or numeric characters
One of the following abbreviation representations of UCS characters:
NUL, SOH, STX, ETX, EOT, ENQ, ACK, BEL, BS, HT, LF, VT, FF, CR, SO, SI, DLE, DC1-4, NAK, SYN, ETB, CAN, EM, SUB, ESC, FS, GS, RS, US, DEL
or one of the following UCS domains:
U+0000 - U+001F or U+007F
The following glyph representation of UCS character:
.
or the following UCS value:
U+002E
An interleaved sequence of a numerical sequence and a dot character.
If any sub-sequence is not interleaved between a numerical sequence and a dot character, the version is ill-formed.
Well-formed:
0.0.1Ill-formed:
0..1or
0 0.1;TODO; Add more character sets
A binary program that functions exactly as stated in this specification.
A terminal-like program, normally part of the Operating System, that provides an STDIN & STDOUT which the user can interact with.
The program is well-formed according to this specification and will continue forward.
The program is not well-formed according to this specification and will print an error message.
A project is an individual, non-relational, set of certain folders & files that make it possible for the Iris compiler to take these contents as an input and output the result(depending on the configuration options) as another set of files and/or folders.
A sequence of numeric characters.
A sequence of alphanumeric characters. The first character must be an alpha character, otherwise the program is ill-formed.
The minimal project structure, where the project name is the alphanumeric sequence project, would be the following:
project
│
└───docs
│
└───libs
│
└───out
│
└───res
│
└───src
│
│ project.cornea
│
│ project.sclera
This folder with the name of the project is the project folder and it contains all the elements that a project must have.
This project sub-folder should contain all the documentation of your project. The file extension for the documentation must be .lens, and it follows the Lens format specification.
This project sub-folder should contain all the libraries, native or Retina, of your project. The extensions accepted for the native libraries are:
.dll.dylib.framework.so
For the Retina libraries, the file extension must be .retina, and it follows the Retina format specification. These might contain an additional file with the extension .key, which provides to the compiler the hashes that it must use to decrypt the library encoded content.
This project sub-folder should contain all the output of your project generated by the compiler.
Depending at the configuration options provided at the Cornea format, it will produce a Retina library, with an additional, depending on whether or not the encrypt option was set to true at the configuration options, .keys file indicating the hashes used to encrypt such library, or a binary, both with or without their respective documentation, if any.
This project sub-folder should contain all the resources of your project. Any extension is allowed, these files will be copied onto the output resource folder.
This project sub-folder should contain all the source code of your project. The file extension for the source files must be .iris, and it follows the Iris format specification.
This file with extension .sclera, indicates some pre-configuration options of the project that will affect the parsing of all the project files, including the Cornea file.
It follows the Sclera format specification.
This file with extension .cornea, indicates the configuration options of the project.
It follows the Cornea format specification.
The command-line options are given to the Iris compiler to control the following execution. There are 3 options:
versioncreatecompile
If no options are given, the program is ill-formed.
If none of these options are provided, the program is ill-formed.
The version option provides to the output of the command-line the version of the actual Iris compiler, in a version-like format, e.g, the expected output of an Iris compiler with the version 0.0.1, would be the following:
0.0.1
The create option will create at the current directory the project structure neccessary by any Iris project.
It requires an additional alphanumeric sequence determining the project name:
Well-formed:
create projectIll-formed:
create pr@jectIf no project name is provided, the program is ill-formed.
If the project name isn't an alphanumeric sequence, the program is ill-formed.
If the current directory already contains a project folder with the same name as the one being created, the program is ill-formed.
If any of the items of the project structure, including the project folder, couldn't be created, the program is ill-formed.
The compile option will compile with the indicated Iris compiler, at the current directory, the project specified by an additional alphanumeric sequence, indicating the project name:
Well-formed:
compile projectIll-formed:
compile pr@jectIf no project name is provided, the program is ill-formed.
If the project name isn't an alphanumeric sequence, the program is ill-formed.
If any of the items of the project structure, including the project folder, couldn't be found, the program is ill-formed.
Once the compile option starts executing, the Iris binary will enter the compilation pipeline. This is the pipeline where the project files get translated into the resulting output. The order is always the same:
- Sclera phase
- Cornea phase
- Resources phase
- Native libraries phase
- Retina libraries phase
- Lens phase
- Iris phase
- Pupil phase
- Vitreous phase
- Macula phase
- Nerve phase
Please note that some steps happen linearly and others may be occur concurrently.