that means Thomas you have the code completion plug-in enabled ?
Yes, I have it enabled for the odd hope that it might manage with a 1% chance to do a "find definition" correctly when I use a function like
snprintf and want to be sure that I'm giving it the correct parameters. Never does, of course. Winning the lottery is more likely to succeed. So I find myself searching through system headers in Windows Explorer instead, every single time.
If CC only was helpful in, say 50% of all cases, and if it was only popping up shit in, say 5% of all cases, I wouldn't be complaining. But it is really only causing extra work and never helping.
I don't understand why it already hampers daily work enough the way it is now.
Because it's fucking dumb and pops up menus that only ever contain shit. And worse, you have to hit ESC to make them go away. If you type fast, it will happen once or twice per week that you type something like
struct SomeName
{
and find that this super smart code completion silently changed it into
struct SomeShitFromWindowsThatIncidentiallyStartsWithSome
{And once per month, you only notice that after having wasted several minutes on a strange compiler error that you don't understand. Similar thing happens occasionally when changing a variable name in some function. After changing the name and hitting the "up" key 3-4 times (to get to the next line containing the name), you find yourself only scrolling through some flipping popup menu instead of moving the cursor. By the time you've stopped shouting and hitting your monitor with the keyboard, you have forgotten what you actually wanted to change.
Add to that these darn smart braces, which mean that you have double work to fix the indenting for every new scope block, only because the editor deems it a good idea to insert tabs when you never touched the tab key. At least those can be turned off relatively easily in Code::Blocks, but I've yet to find where to disable them in SciTE.
In that sense, I wouldn't want the editor to mess with changing operators silently (and possibly unnoticed). It's the programmer's job to know what operator is the right one, not the editor's. And in this case, it is much more severe than inserting extra tabs (which is only formatting) or inserting some bullshit names (which will not go unnoticed). This is something that even has a realistic (though admittedly small) chance of introducing silent changes which will compile without error, but won't do what the programmer intended.
I mean, you could as well have code completion change all occurrences of
var++ to
++var, how does that sound? It's the very same idea.