From kde-commits  Sun Jan 06 23:47:22 2008
From: Jens Dagerbo <jens.dagerbo () swipnet ! se>
Date: Sun, 06 Jan 2008 23:47:22 +0000
To: kde-commits
Subject: Re: KDE/kdevelop
Message-Id: <200801070047.22307.jens.dagerbo () swipnet ! se>
X-MARC-Message: https://marc.info/?l=kde-commits&m=119966327628741

On Monday 07 January 2008 00.22.10 David Nolden wrote:
> On Sunday 06 January 2008 22:26:27 Matt Rogers wrote:
> > yes, absolutely, and i'm not suggesting that we take it out.
> >
> > is there a way to make this extensible so that it only completes when
> > working on a project that supports foreach?  We don't have to do it
> > now, but it would be a cool feature. :)
>
> What I've done doesn't mean that "foreach" will show up in the
> completion-list. It's just that when foreach(..) happens in the
> source-code, it is understood correctly, by correctly building duchain
> stuff. That means that highlighting, refactoring, etc. will work
> with/within foreach statements. So it doesn't change anything for projects
> that don't use foreach.
>

What happens if the parser runs on code that contains a different "foreach" 
macro than the Qt macro? Since it isn't a reserved keyword this is a 
perfectly possible scenario. Will that break somehow?

// jens