Home » Language IDEs » C / C++ IDE (CDT) » Outline
| Outline [message #166549] |
Fri, 24 March 2006 13:15  |
Eclipse User |
|
|
|
Originally posted by: jgallagher.opendap.org
Hi,
I am having problems with both the indexer and the Outline mode. I Know
there are lots of messages about the indexer; for now I'd like to get
the Outline mode working. The problems seem to be limited to C++ code. I
have several projects which contain a mixture of Perl, C and C++. The
Outline View works fine for the C and Perl code, but not for the C++. In
some cases a few methods/functions will be shown, but others are missing
which is some cases the window shows only includes.
Any clues?
Things I have tried: A fresh install of Eclipse (3.1.2); switching to
ctags indexing, fresh SVN checkouts of projects.
Thanks,
James
|
|
| | | | |
| Re: Outline [message #167565 is a reply to message #166911] |
Thu, 06 April 2006 12:33  |
| Eclipse User |
|
|
|
Originally posted by: jhrg.mac.com
Norbert Ploett wrote:
> James,
>
> the parser which feeds the outline view cares for #ifdefs, so if some of
> your functions are not compiled according to the currently set #defines then
> they will not be shown in the outline. Pre-defined symbols must be made
> known to eclipse in the project properties (exact place depending on whether
> you are using managed or standard make projects).
>
> That it?
Here's what I've figured out so far. Some system headers seem to break
the parser. I rarely include headers in my .h files, so those all work.
That is, the Ouline view for my all of the project's headers seems
complete. If I remove all the system headers from a .cc file, the
outline mode works as long as the class definition is visible. If I hide
the .h file which defines the class, then the outline view for the
implementation is hobbled in that only a handful of the methods are shown.
So there seems to be two issues, one of which is that the system headers
on my machine break the Outline view parser. The other, which may not
matter for my situation since all of my implementation files include a
definition, is that the Outline view is missing methods when the
implementation does not include the definition. That seems odds,
particularly since I didn't notice a pattern to behavior. Regardless,
the first problem really breaks things. And the Outline is one of the
main reasons I use Eclipse.
I'm running Eclipse on Fedora Core 4 with the stock gcc (4.0.0); java
-version returns: Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_04-b05,
mixed mode). My hardware is dual intel 64-bit. In the projects eclipse
properties I removed all defined symbols, so I'm pretty sure I'm not
inadvertanly definining something that messes with the headers. Using
gcc the code compiles correctly.
Thanks very much for your help.
James
>
>
> Norbert
>
>
|
|
|
| Re: Outline [message #167596 is a reply to message #167565] |
Fri, 07 April 2006 03:27 |
| Eclipse User |
|
|
|
Hi James
In order to get the a stable outline I can recommend you a quick hack.
Just disable the
flag "Follow #includes when parsing working copies" in the
C/C++ Properties.
Of course this doesn't correct the obvius disfunction in the CDT, but at
least the outline
is working now.
Hope this helps
andrés
Am 06.04.2006, 18:33 Uhr, schrieb James Gallagher <jhrg@mac.com>:
> Norbert Ploett wrote:
>> James,
>> the parser which feeds the outline view cares for #ifdefs, so if some
>> of your functions are not compiled according to the currently set
>> #defines then they will not be shown in the outline. Pre-defined
>> symbols must be made known to eclipse in the project properties (exact
>> place depending on whether you are using managed or standard make
>> projects).
>> That it?
>
> Here's what I've figured out so far. Some system headers seem to break
> the parser. I rarely include headers in my .h files, so those all work.
> That is, the Ouline view for my all of the project's headers seems
> complete. If I remove all the system headers from a .cc file, the
> outline mode works as long as the class definition is visible. If I hide
> the .h file which defines the class, then the outline view for the
> implementation is hobbled in that only a handful of the methods are
> shown.
>
> So there seems to be two issues, one of which is that the system headers
> on my machine break the Outline view parser. The other, which may not
> matter for my situation since all of my implementation files include a
> definition, is that the Outline view is missing methods when the
> implementation does not include the definition. That seems odds,
> particularly since I didn't notice a pattern to behavior. Regardless,
> the first problem really breaks things. And the Outline is one of the
> main reasons I use Eclipse.
>
> I'm running Eclipse on Fedora Core 4 with the stock gcc (4.0.0); java
> -version returns: Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_04-b05,
> mixed mode). My hardware is dual intel 64-bit. In the projects eclipse
> properties I removed all defined symbols, so I'm pretty sure I'm not
> inadvertanly definining something that messes with the headers. Using
> gcc the code compiles correctly.
>
> Thanks very much for your help.
>
> James
>
>> Norbert
>>
--
Erstellt mit Opera
|
|
|
| Re: Outline [message #167648 is a reply to message #167596] |
Fri, 07 April 2006 17:08 |
| Eclipse User |
|
|
|
Originally posted by: jhrg.mac.com
Andrés wrote:
> Hi James
>
> In order to get the a stable outline I can recommend you a quick hack.
> Just disable the
> flag "Follow #includes when parsing working copies" in the C/C++
> Properties.
>
> Of course this doesn't correct the obvius disfunction in the CDT, but
> at least the outline
> is working now.
>
> Hope this helps
Yes! Thanks for the tip.
James
> andrés
>
>
>
>
> Am 06.04.2006, 18:33 Uhr, schrieb James Gallagher <jhrg@mac.com>:
>
>> Norbert Ploett wrote:
>>
>>> James,
>>> the parser which feeds the outline view cares for #ifdefs, so if
>>> some of your functions are not compiled according to the currently
>>> set #defines then they will not be shown in the outline.
>>> Pre-defined symbols must be made known to eclipse in the project
>>> properties (exact place depending on whether you are using managed
>>> or standard make projects).
>>> That it?
>>
>>
>> Here's what I've figured out so far. Some system headers seem to
>> break the parser. I rarely include headers in my .h files, so those
>> all work. That is, the Ouline view for my all of the project's
>> headers seems complete. If I remove all the system headers from a .cc
>> file, the outline mode works as long as the class definition is
>> visible. If I hide the .h file which defines the class, then the
>> outline view for the implementation is hobbled in that only a handful
>> of the methods are shown.
>>
>> So there seems to be two issues, one of which is that the system
>> headers on my machine break the Outline view parser. The other, which
>> may not matter for my situation since all of my implementation files
>> include a definition, is that the Outline view is missing methods
>> when the implementation does not include the definition. That seems
>> odds, particularly since I didn't notice a pattern to behavior.
>> Regardless, the first problem really breaks things. And the Outline
>> is one of the main reasons I use Eclipse.
>>
>> I'm running Eclipse on Fedora Core 4 with the stock gcc (4.0.0); java
>> -version returns: Java HotSpot(TM) 64-Bit Server VM (build
>> 1.5.0_04-b05, mixed mode). My hardware is dual intel 64-bit. In the
>> projects eclipse properties I removed all defined symbols, so I'm
>> pretty sure I'm not inadvertanly definining something that messes
>> with the headers. Using gcc the code compiles correctly.
>>
>> Thanks very much for your help.
>>
>> James
>>
>>> Norbert
>>>
>
>
>
|
|
|
Goto Forum:
Current Time: Tue Jul 15 05:07:31 EDT 2025
Powered by FUDForum. Page generated in 0.74075 seconds |
Home