Stair is a programming concept for development environments and stands for standardised transformation after individual rules. It provides a programming language Clare (coding language after rule environment), which is capable of learning (by adding rules and meta-rules) and can activate (self-) optimisation algorithms that adapt themselves to the individual circumstances within a narrow time frame and are sufficiently complex, as a reasonable behaviour of the running time and an acceptable effort suggests.
Its rule-based individual notation can be, within the feasible scope, freely chosen and is recorded in (per programming language used) exchangeable modules, which are pooled in a rule environment. It can be, as far as possible, comfortably transformed into any other feasible notation (also into a general standard), after individually selected rules, in order to share it with others. Coding suggestions can be easily selected in the IDE.
By appropriate selecting its modules, it can be kept lean. The use of sample code of the target programming language, which can be, for example, received via the internet, enables also realising code, for that (yet) no favourable rules exist. Since source code is used, the string operations insert, delete and replace are sufficient as basic operations. Modularisation and text editing can also be automated in the target programming language.
Discussion: Stair is interesting if source code is to be converted (on a large scale) at pace into other programming languages. It would seem the thing to do, if these have advanced concepts to maintain the own notation for different programming languages. This avoids a migration and permits to optimise code, or to prove its correctness with further tools.
© 2011-2019 by Boris Haase