Problems and Bugs

  Please see the file Doc/Bugs of the distribution. This section just contains more permanent problems which are unlikely to be fixed.

• IEEE exception handling isn't implemented. Doing so portable is very problematic.
• Static checks on classes with type bounds are not performed. This never affects the correctness of compiled code, but means that for the moment it is possible for a new instantiation of parameters to cause a type problem that wasn't recognized until that instantiation. There is some non-zero chance that Holger may implement this.
• Programs with infinite numbers of classes, for instance

          class BUG{T} is a:BUG{SAME} is end; end;
  

  aren't caught properly; the compiler infinite loops.
• Cycles of value types where each type has an object attribute whose type is the next in the cycle are also not caught. So, don't write programs like this.
• Stack overflows are reported as void accesses under some circumstances, because they are just trapped seg faults.

Bugs affecting invocation/environment:

• Symbolic info generated by -debug or -g may occasionally point to a C file instead of Sather, but these should be ignored (it only happens if there isn't an appropriate Sather line that corresponds to the C statements, such as during automatic boxing of dispatched value types).