Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Build CodeBlocks using Microsoft Visual C++

<< < (7/10) > >>

killerbot:
I have used both, and off course CB is better ;-)
But the debugging experience in Visual Studio is way better, honest is honest [better watches windows, more stable, structures in a watch or mouse over can expand, [the frontend, aka CB part] ... , and way better then GDB (the backend part)]. This is the one of the very little things on my list I would love to see on the same level in CB.

ollydbg:

--- Quote from: killerbot on April 06, 2011, 02:32:06 pm ---I have used both, and off course CB is better ;-)
But the debugging experience in Visual Studio is way better, honest is honest [better watches windows, more stable, structures in a watch or mouse over can expand, [the frontend, aka CB part] ... , and way better then GDB (the backend part)]. This is the one of the very little things on my list I would love to see on the same level in CB.

--- End quote ---
Visual studio's supply two versions of CRT libraries(release, debug). when debugging, the debugging CRT library give the debugger more information.(e.g. the debug CRT library can set the stack to 0xCC when entering a function, so VC debugger can easily catch some uninitialized variable, it can save some stack pointer address value, so it can check the value when the function returned).

but for gdb, it has no idea about this. I do not know whether MinGW CRT library has both release/debug CRT. So, sometimes, gdb try to resolve uninitialized memory(contains random value instead 0xcc), which mostly cause a gdb crash. So, I mostly hope a more stable debugging CRT library under MinGW to support gdb.

PS: GDB's python script can make debugging under GDB much better. MSVC as I know does not has this kind of script support.

Loaden:

--- Quote from: MortenMacFly on April 06, 2011, 01:03:12 pm ---BTW: This will break translations IMHO, as the second part (now _T("")) will not appear in the translation tables. You should always use _("").

--- End quote ---
Bad news, And I can't fix this issue. :(

Ceniza:
I have access to Visual Studio 2010 Professional and Intel C++ Studio XE, which means more tools that could be used to improve C::B if you manage to make it build with it.

I, on the other hand, think that Visual Studio 2010 SP1 + Visual Assist X + Intel C++ Studio XE is much better than C::B, at least from a Windows-only point of view. Price is quite a difference, but the company is paying for it.

MortenMacFly:

--- Quote from: Loaden on April 06, 2011, 02:42:38 pm ---Bad news, And I can't fix this issue. :(

--- End quote ---
Well, you'll need to do something like:
Old:

--- Code: ---_("text....\n"
   "more text...")

--- End code ---
New:

--- Code: ---_("text....\nmore text...")

--- End code ---
...or:

--- Code: ---wxString str = _("text....\n")
                 + _("more text...");

--- End code ---

Navigation

[0] Message Index

[#] Next page

[*] Previous page