I've got two questions for code::blocks I need help with.
1):
Normally, for code::blocks, when I click on build error messages, it jumps to the line of which the error is on. For some reason, however, this is disabled for me - what settings do I have to modify in order to re-enable it?
2):
When using the Find and/or Replace feature, I have trouble optimising the search such that it doesn't bring up false positives (I'm working with 10+ files), for example:
Say I want to replace the return variable of numerous differently name functions, such that:
bool ReturnBool()
bool SomeOtherFunction()
become:
const bool ReturnBool()
const bool SomeOtherFunction()
You would search for 'bool' and replace it with 'const bool'. But my problem is, there already exist instances of 'const bool', of which it picks up, and there are also booleans which are variables (and not function returns) - and there a lot of instances of pre-existing 'const bools', so for example:
bool ReturnBool()
const bool ReturnConstBool()
const bool ReturnConstBool(const bool IsAcceptable)
bool Toggle;
would become:
const bool ReturnBool()
const const bool ReturnConstBool()
const const bool ReturnConstBool(const const bool IsAcceptable)
const bool Toggle; //This is now read only. Which is bad.
Just to add: Whilst it would be an idea to say to manually sift through the code, there are 10+ pages of code to sift through, and this process gets extremely tedious given there are a lot of const bool returning functions. The bool to const bool is a standardising process to check for any functions not compliant - but it catches all the functions that are already compliant.
Is there any way that I could somehow:
1) Specify a 'but not' instance, so for example:
Search for all:
bool
But not:
const bool
Replace with:
const bool
2) Make it avoid replacing instances of pre-existing const bools?
3) Make it avoid variables?
I imagine this isn't likely to get an answer, but would it be worth considering implementing a 'but not' feature?
