[deleted - misplaced due to timeouts]
[oBFus post and mine 'delete' request changes crossed on the wires]
[Readded content to be in correct order (Jens) :]
1. Why do you need such feature? C::B is not intended as a gdb/cdb-only wrapper. It is an IDE with debugging support.
personal need - I am debugging items that cannot currently be built with C::B (borland/codegear/EMBT VCL-based applications), and C::B and GDB are the tools that I have currently chosen to invest in to make this possible (vendor tool usage has "issues".)
general justification - if C::B is the tool one has at hand, and, is familiar with, one should not be be forced to obtain-or-create/install/learn a different tool, when there is no particularly rational reason C::B can't provide that functionality.
question - What _is_ an IntegratedDevelopmentEnvironment?
answer - A set of tools that work well together to support development of applications. In order of anticipated common usage, most to least, that would likely generally include editor/build support/debugger/analysis-documentation tools.
observation - The organization of an IDE should not arbitrarily impose any requirement that tools which (can) work well alone, be unnecessarily structured to require working only with each other, when such "separate" usage architecture does not impose any significant penalty on that combined entity nor the effort involved in implementing it. (If you disagree with this, then perhaps you should consider disabling the ability to use the editor without having a project/workspace open
.) If, the continued separate usage architecture of such tools imposes some significant penalty/requirement that no-one is willing to pay, then perhaps such implementation might be best avoided - but, I have already made the initial investment here, and I don't think the maintenance requirements will be significant.
I do not seek a gdb/cdb-wrapper only
- I seek a tool that will serve me reasonably in various situations.