Re: [cdt-core-dev] STRUCTURAL_PARSE in the outline confusions

[John Camelon <jcamelon@xxxxxxxxxx>]

cdt-core-dev-admin@xxxxxxxxxxx wrote on 08/11/2004
12:35:36 PM: 
> > Concern 3: 
> > STRUCTURAL_PARSE requires include paths in order to work properly.
 Since 
> > we have not done integrations to all toolchains as of yet, we
would be 
> > disabling the outline view out of the box for non-GNU clients.
> > STRUCTURAL_PARSE/COMPLETE_PARSE without include paths is even
less 
> > accurate than QUICK_PARSE. 
> > 
> 
> You will __always__ have trouble for this level of integration, unless
you
> distribute the entire headers, libraries, compiler .. and OS.  Since
> you have control
> you can set things properly.  For free style projects like "standard
make"
> it will be up to the user to set things correctly, control is in there
hands.
> We help by providing tools like the "auto discovery", we
are working on
> "GCC container path entries" etc ...
> 
> IMHO, to penalize everybody because of this, is taking a few step
back.
> CDT is a free IDE, it is not possible to provide n configurations
for all the
> m variations of OS, libraries, headers ...

I think we need to come up with a Win/Win regarding
this.  We need to find a way to 
effectively support both types of customer, the kesselhaus
as well as the newbie. What
I'd like to eventually see is some heuristics applied
to each project from the CModelBuilder
to figure out when we are best off using STRUCTURAL
vs. QUICK parse, assuming that we can
eventually get things parsing quick enough.  

JohnC