--- /opt2/src/codeblocks/src/sdk/propgrid/Makefile.am 2007-11-01 18:21:40.000000000 +0100
+++ src/sdk/propgrid/Makefile.am 2007-11-03 14:47:17.000000000 +0100
@@ -1,4 +1,4 @@
-INCLUDES = $(WX_CXXFLAGS) \
+INCLUDES = $(WX_CXXFLAGS) $(GTK2_CFLAGS) \
-I$(top_srcdir)/src/include/propgrid/include
AM_CPPFLAGS = -DWXMAKINGLIB_PROPGRID -DwxPG_USE_WXMODULE=0
#include <iostream>
#include <cstdlib>
int lol();
using namespace std;
int main() // #Here
{ // #Here
int k = 1;
lol();
k = 3;
++k;
k = 34;
std::cout << k++;
std::cout << k++;
std::system("pause");
return 0;
}
int lol() // #Here#
{ // #Here#
int XDF = 4;
XDF =3;
XDF += 4;
return XDF;
}
I don't think that this is a bug.
You are trying to look at a variable outside it's scope ( the { } ), but there it isn't defined. So the output from Code::Blocks is fine.
It is like using a not initialized variable: the results will be random. ^^
Possible fix for "always rebuilds files" case with gcc 4.2.x (bug #12167). You need to rebuild depslib and compiler plugin for the fix to take effectYay, it works again, and my .depend file is back. :)
However, I mean when you "stepped into the scope" the watch still displays wrong number. i.e.when stepped on function "int lol()" call, it's wrong number, when stepped on ++k, it still wrong number, so does k =34; std::cout << k;.........well but the "cout" still produce the correct result. That's why I suspect the watch is broken in some way.....
again, thx for reply.However, I mean when you "stepped into the scope" the watch still displays wrong number. i.e.when stepped on function "int lol()" call, it's wrong number, when stepped on ++k, it still wrong number, so does k =34; std::cout << k;.........well but the "cout" still produce the correct result. That's why I suspect the watch is broken in some way.....
Nah, it's not a bug. ^^
++k is resolved after the debugger stopped there, that's the reason why it shows the false number.
If you would put a breakpoint the line after, it should show correct output.
You'll find the same behaviour in Microsofts Visual Studio, if I remember right.
Just one thing, my dll is 2.7 MO bigger than the one provided by killerbot. May be, he has stripped it.