New issue 13 by TakaoKotani: A simple test system for fparser. r33 caused
errors.
http://code.google.com/p/f2py/issues/detail?id=13
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.
Attachments:
fparsertest.tar.gz 2.0 MB
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
With the r35 I get only missing include file errors.
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).
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.
OK. Could you do it in your next revision?
Comment #5 on issue 13 by pearu.peterson: A simple test system for fparser.
r33 caused errors.
http://code.google.com/p/f2py/issues/detail?id=13
Fixed in r36.