Request: Compare Intel Fortran and Visual Fortran

[shuttledude]

Can anyone tell me if Intel Fortranuses the Win32 API functions for window construction, drawing, etc., or if a .NET type of class library wraps this functionality? The Compaq Visual Fortran makes heavy use of Win32, and I amhoping thatIntel has wrapped this mess up for use in the .NET environment.

Can anyone please comment about this? The more details you can provide, the better.

Thanks!

[Steven_L_Intel1]

The Intel Visual Fortran implementation of QuickWin is pretty much identical to that of Compaq Visual Fortran, and uses the Win32 API. Intel Visual Fortran makes no use at all of the .NET environment.

[shuttledude]

Disappointed with this information, but not surprised. THANK YOU very much for your fast reply!

[Steven_L_Intel1]

I am curious - what benefit did you envision from our reimplimenting QuickWin as a .NET wrapper? That would mean such applications would run only on those systems where the .NET Framework was installed.

[shuttledude]

I was simply hoping to get away from the heavy use of directly invoked Win32 API programming. For example, the old Win32 programming environment was greatly improved with the advent of the C++ MFC classes, and has been even much further improved with the new framework class library in .NET . So many things have been made much simpler by the wrapper classes hiding all the complexity of the Win32 APIs. I never was much of a pure Win32 programmer (a-la-SDK style), and those wrapper classes saved me much grief.

Also --the reason I thought Intel would have wrapped using .NET classes (instead of other types of wrapper classesthat are non-.NET specific, e.g., something similar to MFC design) is that the preferred (in fact, the required) development IDE is the .NET 2002 or 2003 environment.

Anyway, I guess I was thinking a little too much about this! Maybe a future version will really do away with some of the Win32 calls??? Hope so!

Thanks again for your responses.

[Steven_L_Intel1]

Don't confuse the IDE with the run-time environment. They are distinct.

I see now that you are referring to the Win32 API interfaces and not QuickWin. Intel Fortran provides declarations for most WIn32 API routines, but we're not in the business of inventing wrappers for Microsoft APIs. That's Microsoft's job. It would be an extremely daunting task to try to package (and document!) wrappers for the thousands of API routines.

Let me suggest instead one of the many excellent Fortran-friendly libraries for user interfaces and graphics, including Jugoslav Dujic's XFTand commercial products such as Winteracter (available now) and GINOMENU (probably soon.)

We do offer the QuickWin environment as a simple way of getting graphics and a Windows UI into your Fortran program. It isn't as powerful as some other solutions, but is very easy to use.

[svani123]

Hello,

Could u please tell me is CVF development going to be stopped? . As I have been reading few articles that all the CVF 6.6 applications are to be ported to IVF 8.0.

Because, I am presently working on a large QuickWin application which uses lot of graphics and win32API.

In case we have to port to IVF 8.0 , Should I change anything in my source code so that it will be compatible with new Intel Visual Fortran 8.0

What are the similar features to CVF 6.6 and IVF8.0 and What are not similar in between them, Could anyoneof you please tell me clearly so that I can see if my source code compatibility with the new Intel Visual Fortran 8.0.In my source code i am using lot of mod files like DFLib , DFWin,and some local modules.

Waiting for your answers..

Thanks,

[Steven_L_Intel1]

I responded to your basic question in the "Announcing" thread.

HP has said that there will be no further development of CVF.6.6C is the last release.