User forums > Using Code::Blocks
CC: does not list "allocate", a member function of std::allocator.
edison:
The svn 9884 build for ubuntu of Jen's does works, allocate() show in the CC list.
So it is Windows only problem?
Huki:
If there are multiple copies of the header file I'm not sure which one the code completion plugin will use (or even whether it consistently uses the same header). And mingw-w64 has different files like these:
--- Code: ---\mingw32\lib\gcc\i686-w64-mingw32\4.8.1\include\stdint.h
\mingw32\i686-w64-mingw32\include\stdint.h
--- End code ---
etc..
ollydbg:
--- Quote from: Huki on September 05, 2014, 04:46:08 pm ---If there are multiple copies of the header file I'm not sure which one the code completion plugin will use (or even whether it consistently uses the same header). And mingw-w64 has different files like these:
--- Code: ---\mingw32\lib\gcc\i686-w64-mingw32\4.8.1\include\stdint.h
\mingw32\i686-w64-mingw32\include\stdint.h
--- End code ---
etc..
--- End quote ---
CC first try to locate all the search dirs when start a "batch parse"
See: const wxArrayString& NativeParser::GetGCCCompilerDirs(const wxString &cpp_compiler)
When parsing files, it see the #include "xxx.h", then try to search xxx.h file through all the search dirs, and use the first found file, see
wxString ParserBase::GetFullFileName(const wxString& src, const wxString& tgt, bool isGlobal)
edison:
I did add "allocate" to the 2nd Keywords set(settings -> editor -> syntax highlighting), the color of "allocate" was changed as the keyword color setting. But CC still not worked when typing allocate as a member function of a allocator object and set -std=c++11 in compiler settings(Windows 8.1).
btw, Can cb_share_config transfer Keywords setting ? it seems not works via transfer syntax highlighting settings.
ollydbg:
--- Quote from: edison on September 09, 2014, 06:19:52 pm ---But CC still not worked when typing allocate as a member function of a allocator object and set -std=c++11 in compiler settings(Windows 8.1).
--- End quote ---
I guess it is a parse issue by our CC parser, but sorry I can't reproduce this bug in my testing environment. :(
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version