Re: [cdt-core-dev] CDT Core Model API changes

["Alain Magloire" <alain@xxxxxxx>]

> 
>  
> I think that the intention is that you are not limited to a single
> ISourceRoot container,
> but that that would describe the top of a potential tree with various
> includes/excludes
> being described below it.  This would give you the ability to have many
> "source locations".
>  
> Is this correct Alain?

Yes.

Most folks will not see a difference, as the default is the project itself.
This is the current behaviour.

Usually we separate our workspace into source folders, object folders,
template, icons, resources, includes etc..
So reflecting this in the model will help performance and eliminate side effects,
for example, folder "template/" contains irrelevant snippet of code that should
not be part of ContentAssist or Refactoring.