|
From: David B. (GMail-Singapore) <dav...@gm...> - 2008-02-28 01:15:50
|
Jean-Baptiste,
Thank you very much for taking the time to reply.
Arjen in Norway gave me this solution:
Error Regexp: In file (.*):(\d+)\s*(.*)
Warning Regexp: Warning (.*)
Extra Lines Regexp: ((\w*Error:|\s{4})(.*))
Filename: $1
Line Number $2
Error Message: $3
Which works, but I will try your solution tonight. Again thanks for
taking the time to post.
Regards,
David Baxendale
Home Email Dav...@gm...
------------------------------------------------------------------------
Jean-Baptiste Faure wrote:
> Le Samedi 7 Avril 2007 07:02, David Baxendale a écrit :
>
>> Just recently made jEdit my main editor for coding and modeling work, and
>> I not sure how to code the error pattens for the G95 Fortran Compiler. The
>> G95 error messages are
>>
>> In file rddelf.f:84
>>
>> IFx (NFLDLN(NCASE) == 0) THEN
>> 1
>> Error: Unexpected array reference at (1)
>> In file rddelf.f:98
>>
>> ENDIF
>> 1
>> Error: Expecting END SUBROUTINE statement at (1)
>> Process g95 exited with code 1
>>
>> Once I get this to work and a few other things, then I'll post everything
>> to the jEdit and G95 Fortran websites, so that other Fortran users can
>> move to jEdit.without much hassle.
>>
>
> I did the following :
>
> - Error regexp : In file (.*):(\d+)\s*(.*)
> - Warning regexp : (.*):(\d+):\s*warning\s*(.*)
> - Extra lines regexp : (.*)
>
> and it works well for g95.
> Be sure to clic the small key in ErrorList window in order to see the error
> message when it has several lines.
>
> It seems g95 has two kinds of warning message, first kind is similar to error
> message and the second has only one line. Warning regexp matches the second
> kind although Extra lines regexp matches first kind and error messages.
>
> Example of first kind :
> In file toto.f90:834
>
> type (profilAC) :: pAC
> 1
> Warning (137): Variable 'pac' at (1) is never used and never set
>
> Example of second kind :
> toto:684: warning: ‘geometrie_section_MP_largeur.result’ may be used
> uninitialized in this function
>
> You can try these error patterns by adding -Wall option to g95 command line.
>
> Best regards
>
|