Re: Inline::F2003 - New ILSM proposed

[email protected] (Ron Grunwald via inline) Fri, 3 Nov 2017 07:52:02 +0800
Newsgroups perl.inline
Message-ID <[email protected]>
--Apple-Mail=_6C2300CB-B3C9-426B-B1A7-7D621F1A6B66
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

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.

The URL is https://sourceforge.net/projects/inline-f2003/ =
<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.

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.

Cheers,
Ron.
________________________________________
Ron Grunwald
[email protected]
http://www.dvlcorner.org

> On 22 May 2017, at 9:55 pm, Ron Grunwald via inline <[email protected]> =
wrote:
>=20
> Hello all,
>=20
> I've been thinking about this for quite some time now, and have =
finally decided to pursue the idea of a modern FORTRAN Inline module. =
Given that soon I'll be having some time available through to the end of =
this year, I'm confident that I can make this work.
>=20
> The name of the proposed module is Inline::F2003
>=20
> The module will only work for compilers that are compliant with the =
FORTRAN 2003 standard and above. The reason for this is that FORTRAN =
2003 introduced a new feature named "C Interoperability". This feature, =
coupled with Inline::C, are the core mechanisms that will make =
Inline::F2003 work.
>=20


--Apple-Mail=_6C2300CB-B3C9-426B-B1A7-7D621F1A6B66
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Hi all,<div class=3D""><br class=3D""></div><div class=3D"">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.</div><div =
class=3D""><br class=3D""></div><div class=3D"">The URL is <a =
href=3D"https://sourceforge.net/projects/inline-f2003/" =
class=3D"">https://sourceforge.net/projects/inline-f2003/</a></div><div =
class=3D""><br class=3D""></div><div class=3D"">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.</div><div class=3D""><br =
class=3D""></div><div class=3D"">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.</div><div class=3D""><br class=3D""></div><div =
class=3D"">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.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Cheers,</div><div class=3D"">Ron.<br class=3D""><div =
apple-content-edited=3D"true" class=3D"">
<div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; orphans: =
auto; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div =
class=3D"">________________________________________</div><div =
class=3D""><div style=3D"margin: 0px;" class=3D"">Ron Grunwald</div><div =
style=3D"margin: 0px;" class=3D""><a href=3D"mailto:[email protected]" =
class=3D"">[email protected]</a></div><div style=3D"margin: 0px;" =
class=3D""><a href=3D"http://www.dvlcorner.org" =
class=3D"">http://www.dvlcorner.org</a></div></div><div class=3D""><br =
class=3D""></div></div></div><div><blockquote type=3D"cite" =
class=3D""><div class=3D"">On 22 May 2017, at 9:55 pm, Ron Grunwald via =
inline &lt;<a href=3D"mailto:[email protected]" =
class=3D"">[email protected]</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><meta =
http-equiv=3D"Content-Type" content=3D"text/html charset=3Dus-ascii" =
class=3D""><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space;" class=3D""><div =
class=3D""><font face=3D"Avenir Next" class=3D""><div class=3D"">Hello =
all,</div><div class=3D""><br class=3D""></div><div class=3D"">I've been =
thinking about this for quite some time now, and have finally decided to =
pursue the idea of a modern FORTRAN Inline module. Given that soon I'll =
be having some time available through to the end of this year, I'm =
confident that I can make this work.</div><div class=3D""><br =
class=3D""></div><div class=3D"">The name of the proposed module is =
Inline::F2003</div><div class=3D""><br class=3D""></div><div =
class=3D"">The module will only work for compilers that are compliant =
with the FORTRAN 2003 standard and above. The reason for this is that =
FORTRAN 2003 introduced a new feature named "C Interoperability". This =
feature, coupled with Inline::C, are the core mechanisms that will make =
Inline::F2003 work.</div><div class=3D""><br =
class=3D""></div></font></div></div></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_6C2300CB-B3C9-426B-B1A7-7D621F1A6B66--