Repository navigation
Error Messages and Static Analysis #11
Description
Less-Java does not implement any kind of static analysis.
If a less-java program makes it through the front end of the compiler without error, then there is a chance that other semantic errors will be exposed when the generated java source is compiled. In this case, java displays error stack traces referencing objects and line numbers in the generated source. This makes debugging especially frustrating.
Solutions:
- Implement sufficient static analysis
- Parse the output and map the references back to the less-java source
Activity
lam2mo commentedon Apr 17, 2018
Items from wiki:
lam2mo commentedon May 29, 2019
This (or at least a significant part of it) is now part of @hinescd's thesis.
hinescd commentedon Mar 2, 2020
Currently all that's left for resolving this issue is static analysis for method calls (making sure they exist and are visible, etc.)
lam2mo commentedon Apr 23, 2020
@hinescd is this resolved now?