Hi Rob, Thank you for your suggestions and thank you for trying to run the program on your system.
For MS Windows and Apple OS X I have done zero testing, so I'm not surprised that it failed. For the next release I will focus on those two OS's and introduce support for a fourth compiler - Intel Fortran. In relation to listing your name in the README.txt, you have done so much work on Inline and Inline::C in past years, that I thought its only fair to acknowledge your name. However, I will remove it if you really want me to. Finally, my understanding is that Ingy still has the final say on any proposed changes to Inline and Inline::C. Cheers, Ron. > On 3 Nov 2017, at 8:56 am, <sisyph...@optusnet.com.au> > <sisyph...@optusnet.com.au> wrote: > > > From: Ron Grunwald via inline > Sent: Friday, November 03, 2017 10:52 AM > To: inline@perl.org > Subject: Re: Inline::F2003 - New ILSM proposed > Hi all, > >> I'm not sure how many people are still subscribed to this list, but today I >> would like to announce the first release of Inline::F2003. > > It will reach a whole lot more perl folk if you also announce it at > http://www.perlmonks.org/?node=Perl%20News . > (Scroll down to the bottom of that page to get to the relevant text boxes.) > You can post to perlmonks without signing up. > >> The URL is https://sourceforge.net/projects/inline-f2003/ >> There are several reasons why I decided to release the module on Sourceforge >> rather than CPAN. First, I feel that this initial release is not yet >> sufficiently mature to be a standalone CPAN module. The other reason is that >> I'm not sure if the Inline community would allow me to use the "Inline::" >> namespace in the module name. > > There's no reason that you should not use the "Inline" namespace ... and > there are very good reasons that you should *not* use anything other than the > "Inline" namespace. > >> I am highly motivated to produce a high quality module that allows Perl to >> interoperate with modern FORTRAN. This initial release was developed and >> tested on Linux only. However, I would still encourage users to try running >> the program even if their system is non-Linux. >> I am very interested to hear your views and experiences with Inline::F2003. >> It would be great to see discussion reinvigorated on this list. Thank you >> for reading this post. I do hope you'll have an opportunity to tryout the >> program, and report back your findings. > > As a brief preliminary play on MS Windows I ran "perl matopmul.pl" and, > although gfortran is in my PATH, I got: > > C:\s>perl matopmul.pl > ERROR: Key name FOR has invalid value ... gfortran > ERROR: Compiler not found in path! > at matopmul.pl line 0. > INIT failed--call queue aborted. > > I'm thinking that one should turn out to be simple to fix. (I don't have time > right now to look at it.) > > One thing I did notice is that the README.txt lists me as Inline > co-maintainer. Although that might technically be true (not even sure about > that), I haven't been involved in any maintenance of Inline or Inline::C for > a year or two now and, although I still use and take an interest in those > modules, I don't intend doing anything beyond perhaps making bug reports or > submitting patches. > I'm not sure of the state of play at the moment regarding who is doing what > with Inline - though I notice that, according to CPAN, Tina Muller was > responsible for the latest release of Inline::C (version 0.78). > So ... I don't really know whose name(s) should be listed as > "co-maintainers", but I think my name should not. > > Anyway - it's good to finally see an Inline fortran module !! > > Cheers, > Rob > > > >
