Hi,Dennis,
Thanks for your answer.
In fact this is not a very frequent and important problem,your current solution is enough in the rare case that it matters,though i feel instinctively that it can be done just like gdb does in a console,but it may hurt your program's structure,so you don't implement this feature?
As a new SlickEdit user,I'm glad to spread to all my colleagues and friends:
SlickEdit is the best ASM/C/C++ editor I've ever used by now.
But if your company can add some features of Eclipse to it,we'll be more happy and envy Java/Eclipse no more:
1. UML diagram/codegen(I use Umbrello now)
2. more project/build management integration(i'm using cmake now)
3. more version control integration(I'm using subversion now)
4. more TDD integration(unit test and refactor)
5. etc.
I mean not just inclusion of a feature,but the robust and easy use of the feature.As now,the refactor feature is of no much use in a large embedded system project,such as one workspace with Linux kernel and a lot of third party Linux software together,it's natural to put all the stuffs of one project in one workspace,and the refactor will not work in so large workspace.
So, my love to C++/SlickEdit is conservative,and my hate to Java/Eclipse is limited too.