Issue 13 in f2py: A simple test system for fparser. r33 caused errors.

1 view
Skip to first unread message

f2...@googlecode.com

unread,
Mar 24, 2010, 9:28:57 PM3/24/10
to f2py-...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

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

f2...@googlecode.com

unread,
Mar 25, 2010, 6:46:38 PM3/25/10
to f2py-...@googlegroups.com

Comment #1 on issue 13 by pearu.peterson: A simple test system for fparser.

With the r35 I get only missing include file errors.

f2...@googlecode.com

unread,
Mar 26, 2010, 8:23:07 AM3/26/10
to f2py-...@googlegroups.com

Comment #2 on issue 13 by TakaoKotani: A simple test system for fparser.

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).

f2...@googlecode.com

unread,
Mar 26, 2010, 8:26:50 AM3/26/10
to f2py-...@googlegroups.com

Comment #3 on issue 13 by pearu.peterson: A simple test system for fparser.

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.

f2...@googlecode.com

unread,
Mar 26, 2010, 11:55:26 AM3/26/10
to f2py-...@googlegroups.com

Comment #4 on issue 13 by TakaoKotani: A simple test system for fparser.

OK. Could you do it in your next revision?

f2...@googlecode.com

unread,
Mar 26, 2010, 3:58:33 PM3/26/10
to f2py-...@googlegroups.com
Updates:
Status: Fixed

Comment #5 on issue 13 by pearu.peterson: A simple test system for fparser.

Fixed in r36.

Reply all
Reply to author
Forward
0 new messages