[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
28.3 Limitation of the JVM back-end
The JVM back-end supports the entire Bigloo source language but the
call/cc
function. More precisely, using the JVM back-end, the
continuation reified in a call/cc
form can only be invoked in the
dynamic extent of that form.
The other restrictions of the C back-end apply to the JVM back-end. Mainly,
- Bigloo is not able to compile all the tail recursive call without stack consumption (however, most of the tail recursive calls are optimized by Bigloo and don’t use stack activation frames).
- Bigloo compiled applications do not check for arithmetic overflow.
- When compiling to Jvm, the
extern
module clauses are not used. - Jvm runtime system does support the following function
chdir
. - Jvm runtime system support for
chmod
is restricted. - In order to read a shell variable from a Bigloo compiled Jvm program,
you have to use the Bigloo link option
-jvm-env
when linking that program. However, some shell variables are automatically defined (HOME
,USER
,CLASSPATH
andTMPDIR
. - JVM code generation does not support
pragma
forms.
This document was generated on March 31, 2014 using texi2html 5.0.