On 24.12.2015 14:57, Chris wrote:
On Thursday, 24 December 2015 at 09:30:24 UTC, Rainer Schuetze wrote:
In the locals window, mago displays all instances of variables, but
with the same value (which might be some uninitialized value of a
different declaration than expected). The Visual Studio
On 24.12.2015 03:14, Chris wrote:
Please see the linked screenshot: http://i.imgur.com/SpkXu5m.png
As you can see, the inside, outside and collision arrays don't seem to
work with the debugger. They show a bogus lenght and a bogus memory
address. Extracting the lenghts to separate variables
On Thursday, 24 December 2015 at 09:30:24 UTC, Rainer Schuetze
wrote:
In the locals window, mago displays all instances of variables,
but with the same value (which might be some uninitialized
value of a different declaration than expected). The Visual
Studio debug engine shows different