Re: Created codegenerator FCodeGen for generating compilable fortran code

2010-06-10 Thread Øyvind Jensen
On 9 Jun, 23:03, Andy Ray Terrel andy.ter...@gmail.com wrote: Instead of creating new branches every time you update your repo I suggest using stgit [0].  You should be careful though because you can mess up and overwrite things, but as long as you are the person pulling and pushing to your

[PATCH 4/4] Created codegenerator FCodeGen for generating compilable fortran code

2010-06-09 Thread Øyvind Jensen
Implemented tests of the generated strings, and a script in test_external/ to test resulting binaries. The existing CCodeGen and related tests was used as templates for the new functionality. --- sympy/test_external/test_codegen_f95_ifort.py | 240 sympy/utilities/codegen.py

Re: Created codegenerator FCodeGen for generating compilable fortran code

2010-06-09 Thread jegerjensen
The above code is also available at http://github.com/jegerjensen/sympy/tree/fortran_codegen (all patches) and http://github.com/jegerjensen/sympy/tree/fortran_free_form2 (For just the 3 first patches) -- You received this message because you are subscribed to the Google Groups sympy-patches

Re: Created codegenerator FCodeGen for generating compilable fortran code

2010-06-09 Thread jegerjensen
Sorry, I didn't know about the tests under doc/. I fixed it in the second patch, and created new branches at github: http://github.com/jegerjensen/sympy/tree/fortran_codegen2 and http://github.com/jegerjensen/sympy/tree/fortran_free_form3 . -- You received this message because you are