Thanks to .peterson. But it is not.

[GoogleCodeExporter]

What you said is not a solution.I made an easy test system.
So please look into it again it. For your convenience.
I set up quick test system.

I have fparserIssueTakao2/ directory in an attatched file. Then
1. I prepare some of my *.F codes which are no # at the begining of each
   line. So, standard fortran codes.
2. Copy your all files in fparser/ to fparserIssueTakao2/.
3. Then I made a TAKAOTEST2.py.
   It works with TAKAOTEST2.py ztoy.F, TAKAOTEST2.py *.F or so.

Then I typed "TAKAOTEST2.py ztoy.F". It works fine. Good.
But "TAKAOTEST2.py *.F" shows many WARNINGS and fparser stops.

I hope you may modify fparser in some way with minimum fixing for my purpose.

For my purpose, just only showing item='....' is somehow helpful; 
how to show only these line analysys only.

regards,
takao

Original issue reported on code.google.com by TakaoKot...@gmail.com on 3 Mar 2010 at 10:35

Attachments:

• fparserIssueTakao2.tar.gz

[GoogleCodeExporter]

I have fixed few fatal errors like analyzing a line `a(0:n)`
that used to raise ValueError.
Some fatal errors still exists like parsing a line `stop "message"`.
I'll fix this later..

It would be nice if for each fatal error you could
create a separate issue so that I could plan fixing
the issues more efficiently (my time on working f2py is
quite limited).

Original comment by pearu.peterson on 4 Mar 2010 at 9:46

[GoogleCodeExporter]

With revison 11, all .F files are parsed successfully.

Btw, I suggest using fparser as a standalone package rather
that copying its files to your application directory.
That is, in f2py diretory run

  python setup.py install

or just add f2py directory to your PYTHONPATH.

And then in your scripts use

  from fparser.api import parse

Original comment by pearu.peterson on 4 Mar 2010 at 7:29

[GoogleCodeExporter]

Original comment by pearu.peterson on 7 Mar 2010 at 11:17

• Changed state: Fixed