Category:Ecstasy: Difference between revisions
Content added Content deleted
(Create initial page for Ecstasy) |
mNo edit summary |
||
Line 14: | Line 14: | ||
{{language programming paradigm|Object-oriented}} |
{{language programming paradigm|Object-oriented}} |
||
{{language programming paradigm|Imperative}} |
{{language programming paradigm|Imperative}} |
||
{{language programming paradigm|functional}} |
|||
{{language programming paradigm|generic}} |
{{language programming paradigm|generic}} |
||
{{language programming paradigm|reflective}} |
{{language programming paradigm|reflective}} |
||
The '''Ecstasy''' programming language is designed to support the efficient composition of secure applications, long-term maintainable infrastructure, and the efficient low-cost deployment exemplified by the serverless cloud. The language was created by xqiz.it, developed within the open source "Ecstasy Project" organization, and freely licensed using the business-friendly Apache 2 open source license. |
The '''Ecstasy''' programming language ('''xtclang''') is designed to support the efficient composition of secure applications, long-term maintainable infrastructure, and the efficient low-cost deployment exemplified by the serverless cloud. The language was created by xqiz.it, developed within the open source "Ecstasy Project" organization, and freely licensed using the business-friendly Apache 2 open source license. |
||
One or more Ecstasy source files (`.x` files) are [[Compiler|compiled]] to an intermediate [[bytecode]] executable (`.xtc` file) and executed by the XTC Virtual Machine (XVM). The bytecode is a mid-level IR designed to be efficiently lowered to native machine code by a combination of ahead-of-time compilation and an adaptive JIT. |
One or more Ecstasy source files (`.x` files) are [[Compiler|compiled]] to an intermediate [[bytecode]] executable (`.xtc` file) and executed by the XTC Virtual Machine (XVM). The bytecode is a mid-level IR designed to be efficiently lowered to native machine code by a combination of ahead-of-time compilation and an adaptive JIT. |