[Qt-creator] Some feedback

[Wojtek Piszczek]

Adam Higerd pisze:
> Wojtek Piszczek wrote:
>   
>> Having variable names case autocorrection would be useful as well - 
>> first use of particular variable (declaration) is taken as template for 
>> every occurence in block of code (just like in MS VBA editor) - such 
>> mistakes are often source of compile errors.
>>     
>
> Ew. No. I have to put in my voice AGAINST that. It annoyed the CRAP out 
> of me in Visual Basic back before I learned Qt. The problem with case 
> autocorrection is that sometimes you have different variables in 
> different scopes and the correction doesn't know which one is correct.
>
> Potentially even worse is when you have a global constant in ALLCAPS and 
> a local variable in camelCase, and the two aren't even related. This is 
> particularly troublesome when a system header file defines a constant 
> you don't even know about.
>   
It was just a suggestion. IMO problems you have mentioned are 
(particulary in VB) directly effects of the language and variables 
visibility scope. QT creator parses code on-fly, checking a lot of 
things (probably, just guessing) making dynamic tree of code structure - 
it would not be so hard to precisely tell what the scope of the variable 
is and whether particular occurence is declaration or just use. You are 
right - it may be problem with some global identifiers, but that can be 
solved by doing nothing in such cases.

Or maybe I have just overdosed languages without case control ;-)

Regards

Wojtek Piszczek