- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
doc/theses/andrew_beach_MMath/future.tex
r7eb6eb5 r29c9b23 10 10 \item 11 11 The implementation of termination is not portable because it includes 12 hand-crafted assembly statements. These sections must be generalized to support13 more hardware architectures, \egARM processor.12 hand-crafted assembly statements. These sections must be ported by hand to 13 support more hardware architectures, such as the ARM processor. 14 14 \item 15 15 Due to a type-system problem, the catch clause cannot bind the exception to a … … 24 24 scope of the @try@ statement, where the local control-flow transfers are 25 25 meaningful. 26 \item 27 There is no detection of colliding unwinds. It is possible for clean-up code 28 run during an unwind to trigger another unwind that escapes the clean-up code 29 itself; such as a termination exception caught further down the stack or a 30 cancellation. There do exist ways to handle this but currently they are not 31 even detected and the first unwind will simply be forgotten, often leaving 32 it in a bad state. 33 \item 34 Also the exception system did not have a lot of time to be tried and tested. 35 So just letting people use the exception system more will reveal new 36 quality of life upgrades that can be made with time. 26 37 \end{itemize} 27 38
Note: See TracChangeset
for help on using the changeset viewer.