| 1 |
KNOWN ISSUES - MilescriptCompiler 0.8.1 |
|---|
| 2 |
--------------------------------------------- |
|---|
| 3 |
|
|---|
| 4 |
- There are currently issues with the instanceof operand. Its behavior |
|---|
| 5 |
is erratic. This is a very high priority. |
|---|
| 6 |
|
|---|
| 7 |
- A ternary statement as follows: int a = e != null ? 1 : 2; |
|---|
| 8 |
does not parse correctly. However if you put parenthesis around the |
|---|
| 9 |
comparison, i.e. int a = (e != null) ? 1 : 2, then it does parse |
|---|
| 10 |
correctly. |
|---|
| 11 |
|
|---|
| 12 |
- The command line invocation of the MilescriptCompiler does not |
|---|
| 13 |
implement all of the options available via a 'milescriptproject.xml' |
|---|
| 14 |
file. Sample 'milescriptproject.xml' files can be found in the root |
|---|
| 15 |
folders of the Milescript projects included in the 'examples' |
|---|
| 16 |
directory of the Milescript distribution. |
|---|
| 17 |
|
|---|
| 18 |
Run 'java -jar milesc.jar -help' for a full listing of options |
|---|
| 19 |
available via the command line. |
|---|
| 20 |
|
|---|
| 21 |
- The MilescriptCompiler does not recompile a project if the only |
|---|
| 22 |
change to its configuration file was the switching of the debug |
|---|
| 23 |
mode |
|---|
| 24 |
|
|---|
| 25 |
- The 'with' statement currently parses, but is not linked correctly. |
|---|
| 26 |
The Milescript team has not yet decided whether implementing 'with' |
|---|
| 27 |
is worth the effort, given its slow performance in javascript, and |
|---|
| 28 |
its unfortunate ability to block local variables. We could always |
|---|
| 29 |
generate work-arounds for this, but in the meantime, we thought |
|---|
| 30 |
making a temp variable would suffice. We would love any and all |
|---|
| 31 |
feedback on this! |
|---|
| 32 |
|
|---|
| 33 |
- Labeled statements are not being linked/validated correctly. The |
|---|
| 34 |
compiler does not currently reject some labeled statements as it |
|---|
| 35 |
should, nor does it validate that labels provided exist in the |
|---|
| 36 |
namespace. However, they are parsed and generated as typed. For |
|---|
| 37 |
instance, the code below: |
|---|
| 38 |
|
|---|
| 39 |
public void test() { |
|---|
| 40 |
one: |
|---|
| 41 |
for(int i=0; i<10; i++) { |
|---|
| 42 |
if(i > 5) |
|---|
| 43 |
break one; |
|---|
| 44 |
} |
|---|
| 45 |
} |
|---|
| 46 |
|
|---|
| 47 |
will run as expected. However the following: |
|---|
| 48 |
|
|---|
| 49 |
public void test() { |
|---|
| 50 |
int j = 1; |
|---|
| 51 |
one: j = 23; |
|---|
| 52 |
for(int i=0; i<10; i++) { |
|---|
| 53 |
if(i > 5) |
|---|
| 54 |
break two; |
|---|
| 55 |
} |
|---|
| 56 |
} |
|---|
| 57 |
|
|---|
| 58 |
will parse correctly and not throw errors, but |
|---|
| 59 |
will not run in the browser. |
|---|
| 60 |
|
|---|
| 61 |
- Dynamic linking of Milescript applications is not currently |
|---|
| 62 |
implemented. The Milescript team is redesigning the ClassCache, |
|---|
| 63 |
which loads Milescript classes at runtime, We want to implement |
|---|
| 64 |
the ability for the ClassCache to load and run code for multiple |
|---|
| 65 |
Milescript applications at once, while re-using libraries shared |
|---|
| 66 |
between the applications. |
|---|
