paulv
11-14-2006, 08:53 PM
Hello,
It's been more than a year since the 6.2d upgrade to my Lahey linux lf95 compiler. The "News-Newsletter" section of your website hasn't been updated since Winter2005. What are the plans for implementation of a f2003 compiler? Or, implementation of some of the more popular (and easier?) f2003 in context of an f95 compiler? For the latter case I'm thinking about:
1) access="stream". This is implemented in lf95 but still with the non-standard "binary" or "transparent" specifiers. Nearly every other f95 compiler out there now uses "stream" (which == portable code).
2) Full implementation (and support!) for the allocatable array extensions TR 15581.
3) Implementation of the PROTECTED attribute.
...and various others, but you get the idea.
If you guys are working on a full f2003 compilers that's even better but how do we find out what's up and coming at Lahey?
Thanks for any info.
cheers,
paulv
It's been more than a year since the 6.2d upgrade to my Lahey linux lf95 compiler. The "News-Newsletter" section of your website hasn't been updated since Winter2005. What are the plans for implementation of a f2003 compiler? Or, implementation of some of the more popular (and easier?) f2003 in context of an f95 compiler? For the latter case I'm thinking about:
1) access="stream". This is implemented in lf95 but still with the non-standard "binary" or "transparent" specifiers. Nearly every other f95 compiler out there now uses "stream" (which == portable code).
2) Full implementation (and support!) for the allocatable array extensions TR 15581.
3) Implementation of the PROTECTED attribute.
...and various others, but you get the idea.
If you guys are working on a full f2003 compilers that's even better but how do we find out what's up and coming at Lahey?
Thanks for any info.
cheers,
paulv