David Daney wrote: >> (a) if the variable has not been optimized away, gives the location >> where that variable's current value can be found, or >> (b) if the variable has been optimized away, and the value is not a >> constant, says that the value is not available, or > > Perhaps if the variable has been optimized away *but* it is possible to > calculate its value by examining the state of the program, then we can > emit the expression needed to calculate its value in the debugging > information as well.
Yes, that's a good addition. To be clear, I'm not trying to set the goals here; I'm just trying to make sure we have a clear set of objectives and a plan to get there. Thanks, -- Mark Mitchell CodeSourcery [EMAIL PROTECTED] (650) 331-3385 x713
