[hg at technosis.de: [Bug 145687] New: Makeactionfilter fails to parse compiler build output]

[Matt Rogers]

On May 24, 2007, at 7:12 AM, Andreas Pakulat wrote:

> On 23.05.07 20:55:54, Matt Rogers wrote:
>> On Wednesday 23 May 2007 20:20, Andreas Pakulat wrote:
>>> Hi,
>>>
>>> I'd like to apply the patch, but before that I'd like to know wether
>>> there's a reason why the makeactionfilter doesn't filter based on
>>> file extension? If there is I'll commit just the first change he
>>> proposes, else I'll commit the more extensive change which  
>>> simplifies
>>> the regexpes a bit (I can't even read them at the moment).
>>>
>>> Andreas
>>> [snip]
>>
>> the makeactionfiler needs to be able to handle any extension that  
>> can be
>> handled by make. perhaps that's why it wasn't done before. IIRC,  
>> the list
>> includes at least:
>>  - java files
>>  - fortran files
>
> What file extensions are used for fortran?
>

no clue

>>  - C# files
>
> And which for C#?
>

.cs

>>  - C/C++ files
>>
>> So if the regexp can be modified to handle those, it's good.
>
> Yes, basically it'll be a group like
> (\.c|\.C|\.cpp|\.cxx|\.CXX|\.java|...)
>
>> Of course, all of this is moot if the makeactionfilter is only used
>> for c and c++ compilation
>
> I have to check, but I think its used in the makeoutputview, which is
> also used for building custom makefile projects. And these might  
> compile
> any kind of source file in...
>
> Andreas
>
>

sounds like the new regexp should be fine. i doubt many people are  
using KDevelop for fortran work
--
Matt