Developer forums (C::B DEVELOPMENT STRICTLY!) > CodeCompletion redesign
CC's new bug, SVN6049, XPSP3
Loaden:
Operation steps:
1. Create a new C + + project
2. Add # include <vector>
3. In the main function, define a variable: vector <int> v;
4. The next line, enter the 'v.', at the point, after there has been no intelligence tips.
5. Close the current project, and then re-open this project.
6. Repeat step 4, and all normal!
oBFusCATed:
To handle the STL in later gccs (4.0+) C::B needs a patch to be applied (I think).
Also I think, CC does parse only save sources not the once you've just typed (latest patches could have fixed this though)
blueshake:
can not reproduce it.
can you turn debugSmartSense on and post the output here?
MortenMacFly:
--- Quote from: Loaden on January 05, 2010, 12:33:45 pm ---3. In the main function, define a variable: vector <int> v;
4. The next line, enter the 'v.', at the point, after there has been no intelligence tips.
--- End quote ---
Notice that you'll need to save the file for CC to "know" about the newly added code fragments. CC does only know what's been saved.
--- Quote from: oBFusCATed on January 05, 2010, 02:35:22 pm ---To handle the STL in later gccs (4.0+) C::B needs a patch to be applied (I think).
--- End quote ---
Nope, not anymore. This is working fine in SVN trunk meanwhile... soon to be in scintilla / wxpropgrid_debugger branch, too.
--- Quote from: blueshake on January 05, 2010, 02:38:56 pm ---can not reproduce it.
--- End quote ---
Me not, either. Working just fine here... however, I saved before. ;-)
blueshake:
--- Quote ---Me not, either. Working just fine here... however, I saved before. Wink
--- End quote ---
I even don't save the file ,just keep typing. :P
Navigation
[0] Message Index
[#] Next page
Go to full version