search

travellhyne / f2py

Automatically exported from code.google.com/p/f2py
Other
0 stars 0 forks source link

A simple test system for fparser. r33 caused errors. #13

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Hi Attatched is a simple test system for fparser.

Usege:
  expand fparsertest.tar.gz in an empty directory.
  Then run ./job_fatest. No arguments.
  This does svn checkout http://f2py.googlecode.com/svn/trunk/ f2py-read-only
  Then parse fortran codes which are in FfixSample/.

It takes a minute or less. You may remove some codes 
to reduce computational time from FfixSample. Look into job_fatest first.

r33 caused some errors. (r32 did not).
If necessary, I will look into ERRORs furthermore.

Original issue reported on code.google.com by TakaoKot...@gmail.com on 25 Mar 2010 at 1:28

Attachments:

GoogleCodeExporter commented 9 years ago 
With the r35 I get only missing include file errors.

Original comment by pearu.peterson on 25 Mar 2010 at 10:46

GoogleCodeExporter commented 9 years ago 
For example, I saw message as
--------------
  175:      include "mpif.h" <== 'mpif.h' not found in ':.'. The INCLUDE line will be
turned to a comment.
--------------

And this is now classified to ERROR. How to avoid this message?
(I don't think this is an ERROR).

Original comment by TakaoKot...@gmail.com on 26 Mar 2010 at 12:22

GoogleCodeExporter commented 9 years ago 
I made this ERROR because compiler would consider as error.
Since fparser does not have to be so strict, I can make it
warning again.

Original comment by pearu.peterson on 26 Mar 2010 at 12:25

GoogleCodeExporter commented 9 years ago 
OK. Could you do it in your next revision?

Original comment by TakaoKot...@gmail.com on 26 Mar 2010 at 3:55

GoogleCodeExporter commented 9 years ago 
Fixed in r36.

Original comment by pearu.peterson on 26 Mar 2010 at 7:57