dfa.nim: clarify exception handling
This commit is contained in:
parent
fcca59e415
commit
33cdae8c32
1 changed files with 4 additions and 1 deletions
|
|
@ -21,7 +21,10 @@
|
||||||
## Contrary to popular belief, exception handling doesn't cause
|
## Contrary to popular belief, exception handling doesn't cause
|
||||||
## many problems for this DFA representation, ``raise`` is a statement
|
## many problems for this DFA representation, ``raise`` is a statement
|
||||||
## that ``goes to`` the outer ``finally`` or ``except`` if there is one,
|
## that ``goes to`` the outer ``finally`` or ``except`` if there is one,
|
||||||
## otherwise it is the same as ``return``.
|
## otherwise it is the same as ``return``. Every call is treated as
|
||||||
|
## a call that can potentially ``raise``. However, without a surrounding
|
||||||
|
## ``try`` we don't emit these ``fork ReturnLabel`` instructions in order
|
||||||
|
## to speed up the dataflow analysis passes.
|
||||||
##
|
##
|
||||||
## The data structures and algorithms used here are inspired by
|
## The data structures and algorithms used here are inspired by
|
||||||
## "A Graph–Free Approach to Data–Flow Analysis" by Markus Mohnen.
|
## "A Graph–Free Approach to Data–Flow Analysis" by Markus Mohnen.
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue