Category:Mirah: Difference between revisions
m (Added lang tag name) |
m (More links, more lang template params) |
||
Line 1: | Line 1: | ||
{{language |
{{language |
||
|tags=mirah |
|tags=mirah |
||
|express=implicit |
|||
|checking=static |
|||
|site=http://www.mirah.org/}}Mirah is a new way of looking at [[JVM]] languages. In attempting to build a replacement for [[Java]], we have followed a few guiding principals: |
|site=http://www.mirah.org/}}Mirah is a new way of looking at [[JVM]] languages. In attempting to build a replacement for [[Java]], we have followed a few guiding principals: |
||
* No runtime library |
* No runtime library |
||
Mirah does not impose any jar files upon you. YOU decide what your |
Mirah does not impose any jar files upon you. YOU decide what your application's dependencies should be. |
||
* Clean, simple syntax |
* Clean, simple syntax |
||
We have borrowed heavily from [[Ruby]], but added static typing and minor syntax changes to support the |
We have borrowed heavily from [[Ruby]], but added static typing and minor syntax changes to support the JVM's type system. The result is pleasing to the eye, but as powerful as Java. |
||
* Metaprogramming and macros |
* [[Metaprogramming]] and macros |
||
Mirah supports various mechanisms for compile-time metaprogramming and macros. Much of the |
Mirah supports various mechanisms for compile-time metaprogramming and macros. Much of the "open class" feel of dynamic languages is possible in Mirah. |
||
* No performance penalty |
* No performance penalty |
||
Because Mirah directly targets the |
Because Mirah directly targets the JVM's type system and JVM [[bytecode]], it performs exactly as well as Java. |
Revision as of 13:57, 29 August 2011
This programming language may be used to instruct a computer to perform a task.
Official website |
---|
Type expression: | Implicit |
---|---|
Type checking: | Static |
Lang tag(s): | mirah |
See Also: |
|
Mirah is a new way of looking at JVM languages. In attempting to build a replacement for Java, we have followed a few guiding principals:
- No runtime library
Mirah does not impose any jar files upon you. YOU decide what your application's dependencies should be.
- Clean, simple syntax
We have borrowed heavily from Ruby, but added static typing and minor syntax changes to support the JVM's type system. The result is pleasing to the eye, but as powerful as Java.
- Metaprogramming and macros
Mirah supports various mechanisms for compile-time metaprogramming and macros. Much of the "open class" feel of dynamic languages is possible in Mirah.
- No performance penalty
Because Mirah directly targets the JVM's type system and JVM bytecode, it performs exactly as well as Java.
Subcategories
This category has the following 3 subcategories, out of 3 total.
@
- Mirah examples needing attention (empty)
- Mirah Implementations (empty)
- Mirah User (empty)
Pages in category "Mirah"
The following 21 pages are in this category, out of 21 total.