dev:rts:start
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| dev:rts:start [2014/07/01 08:48] – external edit 127.0.0.1 | dev:rts:start [2022/12/20 11:27] (current) – ursgraf | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Runtime System (RTS) ====== | ====== Runtime System (RTS) ====== | ||
| The Java standard library is very powerful and rich. However, as our target compiler puts its focus on efficiency we do not want to support the full library. Some of the base classes, notably java/ | The Java standard library is very powerful and rich. However, as our target compiler puts its focus on efficiency we do not want to support the full library. Some of the base classes, notably java/ | ||
| - | The RTS is described in [[software: | + | The RTS for users is described in [[runtime_library: |
| * [[.: | * [[.: | ||
| Line 9: | Line 9: | ||
| ===== Content of the RTS ===== | ===== Content of the RTS ===== | ||
| - | We use the Java library from the Android project. It stands under the Apache Licence 2.0 and we can alter any class with ease as we also release the target library under the same licence. Some classes can be taken directly, several classes must be simplified or modified. These classes are marked by implementing a special marker interface (//ch.ntb.inf.deep.marker.Modified// | + | We use the Java library from the Android project. It stands under the Apache Licence 2.0 and we can alter any class with ease as we also release the target library under the same licence. Some classes can be taken directly, several classes must be simplified or modified. These classes are marked by implementing a special marker interface (//org.deepjava.marker.Modified// |
| Currently, the class path of a deep project must include the target library with the runtime system. This allows the java compiler to find and resolve its classes when translating into Bytecode. Further, the deep project file must include the path to the class files of the runtime system in order to translate from Bytecode into machine code. | Currently, the class path of a deep project must include the target library with the runtime system. This allows the java compiler to find and resolve its classes when translating into Bytecode. Further, the deep project file must include the path to the class files of the runtime system in order to translate from Bytecode into machine code. | ||
dev/rts/start.1404197315.txt.gz · Last modified: 2016/02/25 13:33 (external edit)
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
