Re: [anjuta-devel] RFC: Symbol-db future

[Naba Kumar <naba kumar gmail com>]

Hi Jhs,

On 12/11/10, Johannes Schmid <jhs jsschmid de> wrote:
> Just to be clear, gtk+ discourages including single header files and
> gtk+-3.0 will only allow <gtk/gtk.h> as valid include and error out
> otherwise. So, I disagree that this is generally considered bad practice.
That's interesting. Primary reason people didn't like
one-include-for-all has to do with optimizing build time. If gtk+ is
changing the policy, then I would assume something must have improved
in gcc that voids the disadvantage. Anyways, that's good news in
general.

> I don't know how limiting to one level could work and I don't think that's
> useful.
If gtk+3.0 is following single include policy, and by extension all
gtk+/gnome modules (because they would all follow suite), then we
actually have to reconsider the importance of this feature. Libraries
will be either all-in or all-out in a file's scope. Our fix to
limiting autocomplete/symbols to project dependency is equivalent to
it for all purposes.

In the end, what's more useful would be to fix
https://bugzilla.gnome.org/show_bug.cgi?id=623735 such that instead of
user selecting a list of libraries for autocomplete, the symbol-db
would automatically take the project dependencies. That way, we can
even get rid of the preferences selection - which seems quite
artificial anyways.

Regards,
-Naba