What is going on with Lahey?
nobat
compiler to Windows 64 at the end of 2005. No new product -- no new
newsletter-- no roadmap for Fortran 2003 implementation? Are they out
of business?
John Fredrickson
news:1170094994.9...@k78g2000cwa.googlegroups.com...
Effective immediately, Lahey Computer Systems, Inc. has appointed Polyhedron
Software Limited as its exclusive global distributor. Through this alliance,
Polyhedron will sell and provide technical support for all Lahey products.
Lahey made this decision so that it can concentrate on further development
and maintenance of its language systems products and porting services.
Polyhedron, located near Oxford in the UK, has been supplying services and
software solutions to Fortran and related markets since 1986, and is widely
respected for its technical expertise and customer service. Polyhedron can
be contacted via email at lahey...@polyhedron.com or visit their website
at http://www.polyhedron.com.
Polyhedron has contracted with Tallac Technology LLC of Truckee, California
to distribute Lahey products within North America. Tallac was co-founded by
John Swenson, Lahey's former vice president of sales and marketing. Tallac
Technology can be contacted via email at sa...@tallactech.com or visit their
website at http://www.tallactech.com.
nobat
partnership with Polyhedron. But I don't see how this is related to my
questions?
Will there be a PathScale compiler for Windows? When? (1 month 1 year,
10 years)
Are they commited to implement Fortran 2003? (incremental
implementation? when? which features will be implemented first?)
Are they products Vista Ready?
....
And all pertinent information that shows their company is alive ...
On Jan 29, 7:47 pm, "John Fredrickson" <jaf...@verizon.net> wrote:
> "nobat" <sk.no...@gmail.com> wrote in messagenews:1170094994.9...@k78g2000cwa.googlegroups.com...> What is going on with Lahey? They were supposed to brring PathScale
> > compiler to Windows 64 at the end of 2005. No new product -- no new
> > newsletter-- no roadmap for Fortran 2003 implementation? Are they out
> > of business?This announcement was made on the Lahey web site on September 22nd, 2006:
>
> Effective immediately, Lahey Computer Systems, Inc. has appointed Polyhedron
> Software Limited as its exclusive global distributor. Through this alliance,
> Polyhedron will sell and provide technical support for all Lahey products.
> Lahey made this decision so that it can concentrate on further development
> and maintenance of its language systems products and porting services.
>
> Polyhedron, located near Oxford in the UK, has been supplying services and
> software solutions to Fortran and related markets since 1986, and is widely
> respected for its technical expertise and customer service. Polyhedron can
> be contacted via email at lahey.sa...@polyhedron.com or visit their website
> athttp://www.polyhedron.com.
>
> Polyhedron has contracted with Tallac Technology LLC of Truckee, California
> to distribute Lahey products within North America. Tallac was co-founded by
> John Swenson, Lahey's former vice president of sales and marketing. Tallac
> Technology can be contacted via email at s...@tallactech.com or visit their
> website athttp://www.tallactech.com.
dpb
> Actually I am aware of their announcemnet regarding to their
> partnership with Polyhedron. But I don't see how this is related to my
> questions?
>
Have you contacted either Polyhedron or Tallac and asked them? I
guess you could also submit a question as a technical support issue
assuming you have a licensed product and see if that gets any
response.
Certainly from the Lahey site it doesn't appear anything is at all
active. Last maintenance update for 7.1 appeared to be dated 12/04,
but since haven't used a Lahey compiler since DOS 3.3 days, that's
just a very quick perusal in response to your posting, I have no idea
whether technical support questions, etc., are being answered.
Herman D. Knoble
just two days ago and got an answer within 3 or 4 hours.
Also, Lahey/Fujitsu Linux64 Fortran v8.0 is rather recent and
enables true run-time checking for undefined variables, subscripts
out of range, etc. on 64-bit Opterons. That's something that
Pathscale compiler nor Intel Com;iler won't do. (The Intel compiler
(for Liinux) does do some run-time checking and more run time
checking is promised I believe). Lahey has it now.
Skip Knoble
On 30 Jan 2007 07:37:11 -0800, "dpb" <dpbo...@swko.net> wrote:
-|On Jan 30, 7:44 am, "nobat" <sk.no...@gmail.com> wrote:
-|> Actually I am aware of their announcemnet regarding to their
-|> partnership with Polyhedron. But I don't see how this is related to my
-|> questions?
-|>
-|...
-|
-|Have you contacted either Polyhedron or Tallac and asked them? I
-|guess you could also submit a question as a technical support issue
-|assuming you have a licensed product and see if that gets any
-|response.
-|
-|Certainly from the Lahey site it doesn't appear anything is at all
-|active. Last maintenance update for 7.1 appeared to be dated 12/04,
-|but since haven't used a Lahey compiler since DOS 3.3 days, that's
-|just a very quick perusal in response to your posting, I have no idea
-|whether technical support questions, etc., are being answered.
Beliavsky
wrote:
> Lahey Technical support is still excellent. I submitted a question
> just two days ago and got an answer within 3 or 4 hours.
I am glad to hear that. I see that questions in the "User Forums" at
http://www.laheyforum.com/ are still being answered.
I am grateful for the "gifts" of g95 and gfortran, but I am still
willing to pay for commercial compilers. I have been happy with the
Lahey/Fujitsu Fortran 95 compiler -- it is good at detecting standard
conformance and catching programmer errors. I look forward to
purchasing more Lahey/Fujitsu compilers -- especially a full or
partial Fortran 2003 compiler.
awgre...@earthlink.net
recently, Lahey is getting out of the Windows compiler business.
As for runtime checking, I have found that IVF 9.1 is faster and more
thorough than Lahey 7.1 on Windows. Maybe Lahey's Linux 8.0 has made
improvements in this area and leapfrogged over IVF.
Al Greynolds
Beliavsky
> According to one of their representatives that I communicated with
> recently, Lahey is getting out of the Windows compiler business.
Thanks for the information. I am very sorry to hear this. Do you know
if they plan to
work on a Fortran 2003 compiler for Linux?
Herman D. Knoble
does not catch.
Skip Knoble
On 31 Jan 2007 05:57:17 -0800, awgre...@earthlink.net wrote:
-|According to one of their representatives that I communicated with
-|recently, Lahey is getting out of the Windows compiler business.
-|
-|As for runtime checking, I have found that IVF 9.1 is faster and more
-|thorough than Lahey 7.1 on Windows. Maybe Lahey's Linux 8.0 has made
-|improvements in this area and leapfrogged over IVF.
-|
-|Al Greynolds
awgre...@earthlink.net
wrote:
> Al: Please post a short run-time example that IVF catches but LF95 v5.7 or 7.1
> does not catch.
>
> Skip Knoble
Unfortunately, its been several weeks since the last time IVF 9.1
found a uninitialized variable at runtime that Lahey 7.1 did not. All
I remember is that it was in a module procedure.
For years, I have depended on Lahey's runtime checking although I was
aware of some of its quirks. For example, they "set" uninitialized
data to a specific bit pattern (a different one for each data type)
and then check for that pattern at runtime. The problem I ran into is
that their integer(1) pattern was valid data for me!
I have been using Lahey compilers since f77l (only a ~100kB
executable!) in the 1980's. I will miss having an up-to-date version
of one of their Windows compilers. The aforementioned contact with
one of their representatives was for a bug that was known but will
sadly never get fixed.
Al
Herman D. Knoble
You may have been using a Fortran 2003 construct that Lahey (windows)
compiles correctly but does not detect uninitialized variables for. Example,
Derived Type Integer (or Real) array. For more complete lists see:
Table III at: http://ftp.aset.psu.edu/pub/ger/fortran/test/results.txt
and Polyhedron results at:
http://www.polyhedron.com/pb05/win32/diagnose.html
Skip
On 31 Jan 2007 10:19:21 -0800, awgre...@earthlink.net wrote:
-|On Jan 31, 7:41 am, Herman D. Knoble <SkipKnobleL...@SPAMpsu.DOT.edu>
-|wrote:
-|> Al: Please post a short run-time example that IVF catches but LF95 v5.7 or 7.1
-|> does not catch.
-|>
-|> Skip Knoble
-|
-|Unfortunately, its been several weeks since the last time IVF 9.1
-|found a uninitialized variable at runtime that Lahey 7.1 did not. All
-|I remember is that it was in a module procedure.
-|
-|For years, I have depended on Lahey's runtime checking although I was
-|aware of some of its quirks. For example, they "set" uninitialized
-|data to a specific bit pattern (a different one for each data type)
-|and then check for that pattern at runtime. The problem I ran into is
-|that their integer(1) pattern was valid data for me!
-|
-|I have been using Lahey compilers since f77l (only a ~100kB
-|executable!) in the 1980's. I will miss having an up-to-date version
-|of one of their Windows compilers. The aforementioned contact with
-|one of their representatives was for a bug that was known but will
-|sadly never get fixed.
-|
-|Al
awgre...@earthlink.net
On Jan 31, 12:07 pm, Herman D. Knoble <SkipKnobleL...@SPAMpsu.DOT.edu>
wrote: