[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 252985] KDevelop4 Displays computed value in place of type in
From:       Nicolás Alvarez <nicolas.alvarez () gmail ! com>
Date:       2010-10-02 2:42:58
Message-ID: 20101002024258.695D970CED () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=252985


Nicolás Alvarez <nicolas.alvarez@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nicolas.alvarez@gmail.com




--- Comment #1 from Nicolás Alvarez <nicolas alvarez gmail com>  2010-10-02 04:42:57 ---
This happens without #defines too. Just "const int foo=42;" will show "42 foo"
instead of "const int foo". It doesn't happen with typedefs, but it does happen
with "#define MyInt int" since then the parser just sees "int" in the
declaration.

I found the cause in the code, but it looks quite "intentional"...
ConstantIntegralType::toString() returns a nice string representation of the
*value*.

I think showing the value in the tooltip is useful, but it's in the wrong
place. And it should be still showing the type somewhere. The way I imagine the
tooltip in this case is "<type> <name> = <value>"; that is, almost exactly what
the real declaration looks like.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs

[prev in list] [next in list] [prev in thread] [next in thread]