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.
I never can figure out what makes it work (or why it doesnt work the first time). For
example yesterday I was having problems with this statement:
if (myBoolean)
goto exit;
well, havent been able to set a breakpoint on 'goto exit' yet.
NT4+SP4+128MB+CWR6
Chris
On Tue, 21 Dec 1999 06:25:21 -0800 [EMAIL PROTECTED] wrote:
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> >
> > I have noticed this too, it drives me crazy! Only way around
> > it has been to delete and retype some statements to make the compiler
> > recognize the code. Very annoying indeed.
>
> Huh?! Can you clarify -- are you saying that in the editor you just delete
> and then re-type the EXACT same code, and then get different results upon
> compiling that code? You must realize how bizarre that sounds, since the
> compiler doesn't care what happens in the editor.
>
> If you can indeed confirm that the compiler is emitting different object
> code at different times, given identical source and settings, then
> something really weird must be going on (like the compiler quietly failing
> due to lack of memory or something). Can you describe your setup?
> (Platform, OS, system RAM, etc.)
>
> -slj-
This message sent using EMUmail. http://EmuMail.com
