compiler error parsing in kdevelop

Andreas Pakulat apaku at gmx.de
Mon May 21 16:13:34 UTC 2007


On 21.05.07 21:01:48, kitts wrote:
> On Monday 21 May 2007 8:06:46 am Alexander Neundorf wrote:
> > it seems I found the problem, the regexp for getting the filename from the
> > compiler error message is the following:
> >
> > ErrorFormat( "([^: \t]+):([0-9]+):([^0-9]+)", 1, 2, 3 ),
> >
> > where the filename is "([^: \t]+)"
> > Now if the filename has spaces (which may very well be) this doesn't work
> > correctly. I could simply remove the " " from the regexp. This will fix it
> > for me. Are there error messages where this might break the parsing ?
> 
> Sort of OT but im curious... How good is the support for error parsing? Can a 
> user easily extend it?

Not without changing the source and have a goood idea about regexps.

> I am looking forward to using kdevelop with compilers other than gcc but i am 
> not sure how well the error parser in the output view will accept it?

We already try to support compilers besides gcc, see for example recent
fixes to support Sun's compiler.

Andreas

-- 
Your lucky number is 3552664958674928.  Watch for it everywhere.




More information about the KDevelop-devel mailing list