[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jedit-users
Subject:    Re: [ jEdit-users ] G95 Fortran Error Patterns with Error List
From:       "David Baxendale (GMail-Singapore)" <david.baxendale () gmail ! com>
Date:       2008-02-28 1:12:46
Message-ID: 47C60A8E.8010606 () gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


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 David.Baxendale@gmail.com
 

------------------------------------------------------------------------



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
>   

[Attachment #5 (text/html)]

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Jean-Baptiste,<br>
<br>
Thank you very much for taking the time to reply. <br>
<br>
Arjen in Norway gave me this solution:<br>
<br>
Error Regexp: In file (.*):(\d+)\s*(.*) <br>
Warning Regexp: Warning (.*)<br>
Extra Lines Regexp: ((\w*Error:|\s{4})(.*))<br>
Filename: $1<br>
Line Number $2<br>
Error Message: $3<br>
<br>
Which works, but I will try your solution tonight. Again thanks for
taking the time to post.<br>
<br>
<div class="moz-signature">
<title>ThunderBird Signature File</title>
<meta name="Generator" content="Winedit 2000">
<meta name="Author" content="David Baxendale">
<meta name="Keywords" content="Signature">
<meta name="Description" content="ThunderBird Signature File">
<pre class="moz-signature" cols="72"><font color="#000066"><font
 color="#000099">
Regards,



David Baxendale
Home   Email <a class="moz-txt-link-abbreviated" \
href="mailto:David.Baxendale@gmail.com">David.Baxendale@gmail.com</a>  </font>
</font></pre>
<hr size="2" width="100%">
<pre class="moz-signature" cols="72">
</pre>
</div>
<br>
<br>
Jean-Baptiste Faure wrote:
<blockquote
 cite="mid:200802270906.14858.jean-baptiste.faure@cemagref.fr"
 type="cite">
  <pre wrap="">Le Samedi 7 Avril 2007 07:02, David Baxendale a écrit :
  </pre>
  <blockquote type="cite">
    <pre wrap=""> 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.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
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
  </pre>
</blockquote>
</body>
</html>



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

-- 
-----------------------------------------------
jEdit Users' List
jEdit-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jedit-users


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic