Developer forums (C::B DEVELOPMENT STRICTLY!) > CodeCompletion redesign

strong enum support

(1/2) > >>

killerbot:
Could our CC gurus have a quick look on the effort needed to support strong enums types (feature from C++0x).

Here's a little code snippet :


--- Code: ---enum class StrongEnum1
{
    on,
    off
};

enum class StrongEnum2
{
    on,
    off
};

int main()
{
    StrongEnum1 value1;
    value1 = StrongEnum1::on;

    return 0;
}

--- End code ---

Current situation.

While typing the line "value1 = StrongEnum1::on;" :
- StrongEnum1 does not give a completion suggestion, due to this it has to be typed completely manually
- StrongEnum1:: does not provide a suggestion list of the possible enum values.

What do you guys think ?

Loaden:
supported in rev6759. :)

killerbot:
it works perfectly :-)

Super great.

killerbot:
just found one little hickup.

When I tooltip over the enum class type, the tooltip shows 2 things :

enum Foo {}
class Foo {}


where it should only show :

enum class Foo {}

Note from time to time, it only says enum Foo. A bit weird.

NOtice something else, when hovering over a struct it also says :
class FooStruct, where I guess we should say : struct FooStruct , right ?

ollydbg:

--- Quote from: killerbot on December 19, 2010, 09:52:26 am ---just found one little hickup.

When I tooltip over the enum class type, the tooltip shows 2 things :

enum Foo {}
class Foo {}


where it should only show :

enum class Foo {}

Note from time to time, it only says enum Foo. A bit weird.


--- End quote ---

should show "enum Foo". I just reviewed the rev6759, loaden just eat the "class" keyword after enum. so


--- Code: ---enum class StrongEnum1
{
    on,
    off
};
--- End code ---

is indeed becomes:

--- Code: ---enum StrongEnum1
{
    on,
    off
};
--- End code ---




--- Code: ---NOtice something else, when hovering over a struct it also says :
class FooStruct, where I guess we should say : struct FooStruct , right ?
--- End code ---
confirmed, I think this can be fixed easily, I will look into it right now.

Navigation

[0] Message Index

[#] Next page