Re: Next release (9?) of IVF

g_f_thomas · ‎03-10-2005

Two questions:

1. Which features of CVF6.6 that are not currently part of IVF8.1 will be included in the next major release of IVF?
2. Will IMSL thread safe edition be part of the next release of IVF Pro?

Thanks,
Gerry T.

Steven_L_Intel1 · ‎03-10-2005

It's too soon to be able to answer either of these questions.

jeff_ryman · ‎03-11-2005

Is there an estimate of when the next major release will be? I am coming up on the end of my initial support period, and need to decide if the yearly support price will be worth it. Since I am not making a living from using the compiler, the yearly support price is worth it only if there is a guarantee of a major release during the year. If I were using it for my job, the annual support price is just a part of the cost of doing business. Thanks for any info you may be able to give.

Steven_L_Intel1 · ‎03-11-2005

July, I think. We'll have another follow-on release soon thereafter to support VS.NET 2005, which we don't expect to be out by the time of our initial release.

Steven_L_Intel1 · ‎03-12-2005

Actually, I can say that there will be several major and very nice features in the next release, including at least one which CVF had but IVF has not had, and some CVF never had.

g_f_thomas · ‎03-14-2005

Will this new release be for both IVF Standard and IVF Pro? If so, what will be the IMSL added value for IVF Pro? Throughout its tenure, IMSL as packaged with IVF Pro, hasn't changed. Support renewal is ca $650, with $450 going for IMSL. The appeal of support renewal is in getting the latest developments and fixes to the IVF compiler and IMSL. Will the current IMSL 5 be link compatible with the next release of IVF under VS.NET 2005?

Thanks,
Gerry T.

Steven_L_Intel1 · ‎03-14-2005

There will be a new copy of IMSL provided to us by VNI. I don't know how it will be different from the one shipped with 8.1 I do know that the older one was built with a compiler that had bugs in name decoration, so it's possible some applications may not link if you use an older IMSL, but it would be the same using a current 8.1 compiler. We're not testing that combination so you're on your own if you try it.

durisinm · ‎03-18-2005

Will the IVF release to support VS.NET 2005 require that version, or will it still work with VS.NET 2003 and C++.NET 2003?

Mike D.

Steven_L_Intel1 · ‎03-19-2005

2002 and 2003 will still be supported, at least for anything in the next year. We haven't even thought about dropping support for them.

krojas · ‎03-29-2005

Steve- Will we be able to debug in VS.net with IVF9?

Steven_L_Intel1 · ‎03-29-2005

Um, sure, you can now with 8.1. We're not doing away with that.

h-faber · ‎03-30-2005

sblionel wrote:
July, I think. We'll have another follow-on release soon thereafter to support VS.NET 2005, which we don't expect to be out by the time of our initial release.

Hi Steve,
does it mean that around July there will be an Intel (Visual) Fortran Compiler 9.0 out? If so, what are the plans about the 8.1 support concerning time/duration? Might be of importance for me as we'll be migrating Fortran 77 / VMS on some old hardware to MS Windows 2003 / Intel 8.1 which is planned to run and work for the next x years.

Regards,
Harald

Steven_L_Intel1 · ‎03-30-2005

When 9.0 comes out, we will continue to provide support for 8.1, though updates to it will become less frequent and eventually stop. You will be able to have 8.1 and 9.0 on the system side-by-side, though only one at a time can be integrated into VS.NET.