Oh I'm not bashing anyone. I have my share of bugs out there that come and
haunt me from time to time. I'm just saying that this bug is a pain (in
this case I am a user and not a producer).
I'll try to check the disassembly next time to see what is happening.
The other reply to this thread (I forgot who wrote it) that said
that writing brackets around statements really helped - I think you're
absolutely right, I know remember using this to fix the problem.
Chris
At 09:52 AM 12/21/1999 -0800, you wrote:
> >No it is not that silly. But still very strange, I move some code around,
> >write different constructs and then finally when I launch the debugger I
> >can see that there is little dash line beside my line of code and I can
> >finally put a breakpoint on that line.
>
>This is an interesting clarification. Perhaps the problem is simply that
>the dash for a debugger break point isn't available in the other cases, but
>the code has in fact been generated.
>
>Looking at the disassembly is the way to find out for sure if you code is
>there. I'd wager that it'd be much more likely that the debugger's
>breakpoint dash might get lost, than that the compiler just skip code.
>
>On the other hand, it could be a bug. Having bugs in compilers is a major
>pain, but let's none of us forget that we also have each written (and
>shipped) our fair share of bugs...
>
>-David Fedor
>Palm Developer Support
>
---
Christian Vandendorpe ([EMAIL PROTECTED])
http://www.zorglub.com
