| View previous topic :: View next topic |
| Author |
Message |
DanRRight
Joined: 10 Mar 2008
Posts: 2816
Location: South Pole, Antarctica
|
 Posted: Thu Mar 13, 2008 5:26 pm Post subject: Are LIB files made with Intel/DEC Fortran 100% compatible... |
 |
|
| ...with FTN95 ? |
|
| Back to top |
|
 |
PaulLaidler
Site Admin
Joined: 21 Feb 2005
Posts: 7925
Location: Salford, UK
|
| Posted: Thu Mar 13, 2008 6:22 pm Post subject: |
|
|
100%? Unknown in computing circles!
However, your libraries may well work with FTN95.
a) They probably use STDCALL and this is not the default for FTN95
(see IMPORT_LIB on the FTN95 command line and Reference Properties in Plato)
b) Passing character variables can be very tricky. |
|
| Back to top |
|
|
DanRRight
Joined: 10 Mar 2008
Posts: 2816
Location: South Pole, Antarctica
|
| Posted: Thu Mar 13, 2008 6:34 pm Post subject: |
|
|
Thanks Paul,
I missed import_lib and had sometimes unexplainable problems for years with some old libraries in some specific cases. Now it works with all parameters fine |
|
| Back to top |
|
|
DanRRight
Joined: 10 Mar 2008
Posts: 2816
Location: South Pole, Antarctica
|
| Posted: Sat Mar 15, 2008 4:33 pm Post subject: |
|
|
| Forgot to ask. How about other compiler vendors libraries for Windows in general. Did compiler developers followed some sort of standard to make libraries compatible across the platform? Specifically, are chances good to link Lahey/Absoft/gfortran libraries with FTN95? |
|
| Back to top |
|
|
PaulLaidler
Site Admin
Joined: 21 Feb 2005
Posts: 7925
Location: Salford, UK
|
| Posted: Mon Mar 17, 2008 8:43 am Post subject: |
|
|
| I think that most have followed the Microsoft lead and adopted the STDCALL protocol. FTN95 is the exception where STDCALL is not the default. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
