Re: Bug in Debugger?
Re: Bug in Debugger?
- Subject: Re: Bug in Debugger?
- From: "McLaughlin, Michael P." <email@hidden>
- Date: Thu, 30 Apr 2009 16:35:45 -0400
- Acceptlanguage: en-US
- Thread-topic: Bug in Debugger?
On 4/30/09 3:02 PM, "Chris Espinosa" <email@hidden> wrote:
> On Apr 30, 2009, at 7:55 AM, McLaughlin, Michael P. wrote:
>
>> *** Using latest Xcode for a Cocoa document project ***
>>
>> In a header, I define
>>
>> enum {Lat1, Lon0, Lat0, Lon1}; // same as Rect, PostScript
>> orientation
>>
>> In a class header, I have
>>
>> float dispBoundaries[4];
>>
>> In a source file, I have (just as a check)
>>
>> dispBoundaries[Lat0] = Lat0;
>>
>> This code actually works as intended, i.e. dispBoundaries[2] <-- 2.
>>
>> However, the Debugger window shows that it is the *last* (index = 3)
>> element
>> of dispBoundaries[] that changes.
>>
>> This error is perfectly repeatable.
>>
>> Am I missing something here or is this a real bug?
>
> What result are you expecting when you assign an enumerated (integral)
> value to a float in an array?
>
> Chris
>
It is not the value of the resulting float that is in question. In fact,
that much is correct.
The problem is that the integer (enum) Lat0 (= 2), used as an index, should
modify dispBoundaries[2] which it actually does. However, the debugger
window then displays something like
(3.7, 0.002, -2e-8, 2)
where the last 2, newly changed, should be in place of -2e-8, not where it
(falsely) shows up.
--
Mike McLaughlin
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden