#5: some warnings stick around in movitz:dump-image ----------------------+----------------------------------------------------- Reporter: sabetts | Owner: ffjeld Type: defect | Status: new Priority: major | Milestone: Component: compiler | Version: Keywords: | ----------------------+----------------------------------------------------- dump-image prints warnings about undefined functions. After correcting the undefined function reference, the warning shows up again in dump-image, despite no reference in the new code.
#5: some warnings stick around in movitz:dump-image -----------------------+---------------------------------------------------- Reporter: sabetts | Owner: ffjeld Type: defect | Status: new Priority: minor | Milestone: Component: compiler | Version: Resolution: | Keywords: -----------------------+---------------------------------------------------- Changes (by ffjeld):
* priority: major => minor
Comment:
The problem is that it is not recorded which particular function(s) it is that calls some other function. The only thing that gets recorded is "this function has been called". That means it's impossible to undo this even when the calling function is re-compiled, since there may be other functions that have made the same call.
The solution is to record more information, namely, for each function which other functions it calls.
Upon create-image, all such information is re-generated, and so also these lingering warnings will go away.
-
movitz