[Swift-devel] [Bug 106] Improve error messages for double-set and un-set variables

[bugzilla-daemon at mcs.anl.gov]

http://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=106


benc at hawaga.org.uk changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED




------- Comment #1 from benc at hawaga.org.uk  2008-04-08 09:09 -------
t10 is fairly easy to fix (I have a patch that I think does this)

t7 is harder. the variable m is marked as an input (because it is never
assigned to). in the case of a file-mapped variable, that would mean the rest
of execution would assume that the backing file exists at the start. In the
case of a variable that is being used as an in-memory unmapped variable like m,
then the present behaviour doesn't work. There perhaps need to be tighter
constraints on when it is permissible to extract a value from a closed dataset
in this situation.


-- 
Configure bugmail: http://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.