my first post

Alexander Neundorf neundorf at
Tue Dec 6 19:45:08 UTC 2005

On Tuesday 06 December 2005 17:58, Andreas Pakulat wrote:
> On 06.12.05 17:20:27, Tommaso Massimi wrote:
> > Hi all,
> >
> > a KDevelop's strange behavoiur (maybe a bug) is annoing me,
> > so in the paste weeks I digged a bit about it.
> >
> > I found the fault already listed here,
> >
> > I added some details and a question about the source code
> > where I think the problems is, but I had no answer.
> ?? What do you mean? Amilcar do Carmo Lucas added a comment.

He wasn't exactly very verbose ;-)

So this might be the reason too why closing a file is so slow in kdevelop ?

void ProblemReporter::closedFile(const KURL &fileName) 
   QValueList<Problem> problems = 
m_cppSupport->backgroundParser()->problems( fileName.path() , true , true); 

It seems this is done in order to remove the problems reported from this file 
from the problem view if the file is closed.
I just tried with the call to problems() commented out, the FIXME from the 
closed file still disappears from the problem view. So this seems not to be 
the reason.

Anybody else knows why problems() is called there ?
Is it required at all ?
Would m_cppSupport->backgroundParser()->remove(fileName.path()); also do the 
job ?

Work: alexander.neundorf at -
Home: neundorf at                -
      alex at               -

More information about the KDevelop-devel mailing list