• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Variable evaluating improperly
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Variable evaluating improperly


  • Subject: Re: Variable evaluating improperly
  • From: Thomas Wetmore <email@hidden>
  • Date: Mon, 29 Apr 2013 19:54:15 -0400

Compilers often optimize flow of control statements in non-obvious ways (especially if the conditional expression is a compile time constant as it in your case). This can lead to misleading or even impossible seeming representations in debugger windows. Insert a printf statement to see if you really get into the then clause. Of course, this might also completely change any optimization rearrangements. All very Heisenbergian.

Tom

On Apr 29, 2013, at 6:28 PM, koko <email@hidden> wrote:

> A picture is worth a thousands words:
>
> http://highrolls.net/What.png
>
>
> You se the variable be DGProduct in the the variables display with a values of 0.
>
> You se the current location in the source which should only be possible if DGProduct != 0.
>
> What could possibly be the problem?
>
> -koko
> _______________________________________________
> 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


 _______________________________________________
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

  • Follow-Ups:
    • Re: Variable evaluating improperly
      • From: koko <email@hidden>
References: 
 >Variable evaluating improperly (From: koko <email@hidden>)

  • Prev by Date: Re: Variable evaluating improperly
  • Next by Date: Re: Variable evaluating improperly
  • Previous by thread: Re: Variable evaluating improperly
  • Next by thread: Re: Variable evaluating improperly
  • Index(es):
    • Date
    • Thread