[Bug 46684] code completion reacts on dot operator for pointer to struct

[Jesse Yurkovich]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
      
http://bugs.kde.org/show_bug.cgi?id=46684      




------- Additional Comments From yurkjes at iit.edu  2004-01-14 23:24 -------
Thats odd because I _hate_ passive popups :)  Underlining errors is currently not possible right now but will be soon in the future.  This, however, is a no-brainer change if you ask me.  It should be fairly simple to switch to the right operator and it's saved me lots of times.  Compared to some of the things kdevelop is doing internally, this is pale in comparison as long as kdevelop gets the proper type of a variable (pointer or not) and then checks to see if it has overloaded methods.  I believe it's that simple to detect.

If you do change a definition later or switch variable types then, yes, underlining it and including it in the problem reporter output would be the right thing to do.  But as long as it can be changed as you type, then why not really?  It's going to do the right thing so why not let it.

The capitalization example was not really suited for this I guess.  But in this case it will always be correct in the 'current' context anyhow -- meaning if you were to compile right then and there it would complete successfully.