andr3/scyther
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

- Note on nested functions.

Browse Source
This commit is contained in:
ccremers 2006-09-13 06:20:44 +00:00
parent 31f1753e4e
commit 420ea29fc4
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
src/todo.txt
View File

@ -1,3 +1,13 @@
- Nested functions should be avoided: their implementation requires an
executable stack, which is bad for security purposes. However, many of
the iterator functions need to pass a function and possibly some
variables. Currently, the variables are handled by the nested function
mechanism (the iterated nested function and address variables of the
function it is part of), which would not work anymore. A possible
solution seems variable argument count functions, but this is fairly
cumbersome and might impact on performance. Alternatively, iterators
can be implemented as macros, which is probably the fastest, but maybe
less readable.
- I've started on sanitizing the --max-attacks switch. It now prunes as a - I've started on sanitizing the --max-attacks switch. It now prunes as a
bound, but it also needs to limit per-claim, I guess. bound, but it also needs to limit per-claim, I guess.
- There is something weird when automatically generating claim labels - There is something weird when automatically generating claim labels