Version: 3.0.0 (using KDE 3.2.0, SuSE) Compiler: gcc version 3.3.1 (SuSE Linux) OS: Linux (i686) release 2.4.21-166-default If I declare a struct like this: typedef struct list { list_entry *start; //!< Pointer to the first element list_entry *end; //!< Pointer to the last element uint32 max_elements; //!< Maximum number of allowed elements uint32 element_count; //!< Current number of elements } list; then only an entry is displayed in the class browser but I can not view the contents of the structure (the + is missing on the entry). Definitions like this work: typedef struct list_entry list_entry; struct list_entry { void *data; //!< Pointer to the data list_entry *next; //!< Next element in the list list_entry *prev; //!< Previous element in the list };
*** Bug 81330 has been marked as a duplicate of this bug. ***
The bug is still present in KDevelop 3.0.3
...and causes code-completion not to work for 'typedef struct' definitions.
I would like to add this comment because I also found out that code completion for "C" does not work for structures typedefs. I will be glad to provide more info if needed.
Is there any news regarding the progress on this bug ? Yesterday, I tried 3.1.0 release, and it's still unresolved there. More then that if in 3.0.x series code completion, at least worked without typedefs : struct aa { int i; int j; }bb; bb.[code completion here] in 3.1.0 code completion here stopped working completely. :(
Are there any news on this bug ? especially in the upcoming new version ?
Seems that "typedef struct xxx" code completion problem persists on Kdevelop 3.2.1, even with: <codecompletion> ... <includeTypedefs>true</includeTypedefs> ... </codecompletion> Project setting "includeTypedefs" set to "true" inside the C++ "codecompletion" options... Note that "struct xxx" code completion does work if not used through the "typedef" mehcanism.
Any word on getting this to work with: typedef struct x_ { /* whatever */ } x; yet? It's very common to write in this style in C, but makes it very annoying that the class browser still refuses to pick this up correctly.
The "word" is that any improvements so far to the cpp parser is taking place in the KDevelop 4 development track. An improvement to the behaviour seen in this bug report is unlikely before KDevelop 4.
*** Bug 147493 has been marked as a duplicate of this bug. ***
fixed in kdevelop4
Moving all the bugs from the CPP Parser. It was not well defined the difference between it and C++ Language Support and people kept reporting in both places indistinctively