Issue 18 in f2py: a callcaller tree generator
f2...@googlecode.com
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 18 by TakaoKotani: a callcaller tree generator
http://code.google.com/p/f2py/issues/detail?id=18
I wrote a small program to generate callcaller tree for Fortran codes.
f_calltree.F file1 file2,... >callcaller.dat 2>callcaller.err
Generate call caller for fortran codes.
Put this just above f2py directory.
I hope you will include this in your fparser package if possible.
(Warning: this cause an error if computer codes are gramatically wrong
when we comment out preprocessor lines. Further, include is not treated
well).
Another point.--
fparser uses yellowtext and so, and ubyte in numpy.
So people need to install numpy only in order to use fparser.
I think this is a little too demanding for people who just want
to use fparser only. So I hope fparser works without numpy.
Attachments:
f_calltree.py 3.8 KB
--
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
Comment #1 on issue 18 by TakaoKotani: a callcaller tree generator
http://code.google.com/p/f2py/issues/detail?id=18
I am trying to develop a little better version. Analysis on
-----------
1.program units.
*Decleared variables.
*Contained program units.
*Identification of I/O of variables. I/O of files.
2.Relations between the units.
-----------
are important things.
f2...@googlecode.com
Comment #2 on issue 18 by pearu.peterson: a callcaller tree generator
http://code.google.com/p/f2py/issues/detail?id=18
The yellowtext, etc can be copied from numpy to f2py but I think
currently the most important usage of numpy within f2py is with
setup.py scripts. I find it more convenient to use numpy.distutils
for packages that contains many standalone subpackages.
May be in future, when fparser becomes more stable, we can remove
numpy dependency, but for now, I think, having numpy around is convenient,
especially because the f2py project will contain in addition to fparser
subpackage also, for example, wrapper generation package that will
require numpy.
About additions to fparser. Please look at the small programs in
fparser/scripts directory, it would be easier to include your scripts
to fparser if you would use the same convention for writing scripts
as these example scripts.
f2...@googlecode.com
Comment #3 on issue 18 by TakaoKotani: a callcaller tree generator
http://code.google.com/p/f2py/issues/detail?id=18
Thank you for your reply.
Since I had installed numpy and so in my machine (ubuntu latest),
no problem to use fparser.
However,I had a problem when I ask my collabolator to use fparser.
He needed to spend a day or so(he is skillful enough),
since he had little knowledge on python.
Now fparser use very limited part of numpy.
Maybe
1 yellow_text, red_text...
2. ubyte.
So, it is probably easy to set a branch when numpy can not find.
--
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
Subscription settings: http://groups.google.com/group/f2py-issues/subscribe?hl=en