|
» Subscribe » Favorite Links » What is S60? » Freeware & Trials » S60 devices » Hints and tips » About this blog |
» Blognotes (15) » Bugs and Workarounds (4) » Build tools (5) » Carbide.c++ 1.1 (4) » Carbide.c++ 1.2 (8) » Carbide.c++ 1.3.x (9) » Carbide.c++ 2.0.x (12) » Carbide Plug-Ins (4) » CodeWarrior (2) » FAQ (6) » Future directions (25) » General (48) » Off-topic (5) » On-device debugging (13) » Performance Investigator (2) » Product features (18) » Product releases (16) » Screencast (14) » Support (36) » Tool setup (6) » UI Designer (8) » Usability (18) » Work in Progress (14) » Write-build-debug (4) |
|
» New Remote Connections View » Terminating Multiple Processes » Agile Tuning of the Austin Team » Introduction to the workspace screencast » Adding DLLs while Debugging |
|
Subscribe to RSS feed For email notification, please click here ยป |
« Carbide.c++ SDK: Reading MMP Statements with the EpocEngine and IMMPData | Main | Quick tip: Where to set post-build options »
You may have noticed the Refactoring menu option in the context menus while using Carbide.c++. Under Carbide 1.3.x all it does is basic renaming of objects and variables. However, there is a project underway (from HSR) that adds a lot of new C++ refactoring functionality to the eclipse C/C++ tool set. You can even give it a test drive by visiting the CDT Refactoring Project website and downloading the update site and installing the plug-ins into Carbide!
I gave this go on a recent Carbide 1.3.1 nightly build by downloading this package and installing it into the plugins and features folder. When you install it and launch Carbide you will notice two new menus.
A Source menu from the menu bar:

and many new items in the Refactoring context pop-up menu:

The basic functionality of renaming, generating getters and setters, and implementing declarations and definitions seem to work pretty well. I haven't tried it on a really complex project though. While this work is largely still experimental it has already been committed to CDT 5.0 and is actively being worked on and improved. As well, under CDT 5.0 there have been many improvements to fixing indexing bugs and we've closed out 10 or so on Symbian specific code under the CDT 5.0 code line. (NOTE: CDT 5.0 and Eclipse 3.4 are the target releases for the next version of Carbide). The future for C++ refactoring under Carbide looks promising.
I do know one refactoring feature I'd like to see: adding new parameters to existing functions. I've added a bug entry if you have any requirements or comments you'd like to add.