Re: [PATCH] initial fcode implementation

2010-03-25 Thread Toon Verstraelen
Right now only f77. f95 is one of the future options I'm thinkng of. Feel free to open a ticket, but I won't forget it anyway. It is mainly a matter of proper line wrapping. cheers, Toon Ondrej Certik wrote: Thanks! Sorry for the late reply. Is this using f77, or f95 syntax? Ondrej On

Re: [PATCH] initial fcode implementation

2010-03-25 Thread Ondrej Certik
On Thu, Mar 25, 2010 at 12:13 AM, Toon Verstraelen toon.verstrae...@ugent.be wrote: Right now only f77. f95 is one of the future options I'm thinkng of. Feel free to open a ticket, but I won't forget it anyway. It is mainly a matter of proper line wrapping. Yes. f77 is fine, it should work in

Re: [PATCH] initial fcode implementation

2010-03-25 Thread Toon Verstraelen
Ondrej Certik wrote: On Thu, Mar 25, 2010 at 12:13 AM, Toon Verstraelen toon.verstrae...@ugent.be wrote: Right now only f77. f95 is one of the future options I'm thinkng of. Feel free to open a ticket, but I won't forget it anyway. It is mainly a matter of proper line wrapping. Yes. f77 is

Re: [PATCH] initial fcode implementation

2010-03-19 Thread Toon Verstraelen
Thanks alot! Vinzent Steinberg wrote: The patch looks fine to me, however I'm not familiar with fortran. But no one objected so far, so I pushed it in, thanks. Vinzent 2010/2/24 Toon Verstraelen toon.verstrae...@gmail.com: --- doc/src/modules/printing.txt | 96 +++

[PATCH] initial fcode implementation

2010-02-24 Thread Toon Verstraelen
--- doc/src/modules/printing.txt | 96 +++ sympy/__init__.py |2 +- sympy/printing/__init__.py |1 + sympy/printing/fcode.py| 326 sympy/printing/tests/test_fcode.py | 217