Community
Participate
Working Groups
My project is using OpenWatcom 1.2 (Standard Make). The keyword __int64 is used in the source (__int64 is a long long). the keyword is recognized by the compiler (i.e. not defined in a header). The indexer flags the __int64 data type as an error.
When we get around to providing a Watcom parser configuration, we can address this.
I think other compilers also support the __int64 keyword (I think MS supports it). It's just not an ANSI keyword (at this time). The keyword might not be widely used at this time. We're bound to see more of it when AMD64 cpu's become more prevalent :-) Reference to the MS support: http://msdn.microsoft.com/library/default.asp?url=/library/en- us/vccelng/htm/basic_45.asp
With slow, it also ocuppies too much memory. In my system, the memory occupied is up to 600M, and increase continuely. My System: CPU: P4 2.4G Memory: 1024M OS: Windows 2000 Eclipse: 3.1.1 CDT: 3.0.1 Compiler: MinGW 3.1 C/C++ project only includes one main.cpp file, the C/C++ indexer occupies 99% CPU Usage and about 500M memory, and takes more than 5 minutes every time I change the source.
No one is currently looking at this. If someone wanted to contribute a Watcom or MSVC parser variant we would welcome the contribution.
Future means you commit to fix it in the Future. Inboxes can't make committments. Moving to '--'.
Duplicate of bug #383773
*** This bug has been marked as a duplicate of bug 383773 ***