View previous topic :: View next topic |
Author |
Message |
DanRRight
Joined: 10 Mar 2008 Posts: 2818 Location: South Pole, Antarctica
|
Posted: Sat Aug 02, 2008 10:56 am Post subject: Can .NET help link the library made in different compiler? |
|
|
Is there any way to trick the FTN95 to accept "foreign body", the library made in another compiler, like its own? If .NET connects other languages, can it do this task too? |
|
Back to top |
|
|
Andrew
Joined: 09 Sep 2004 Posts: 232 Location: Frankfurt, Germany
|
Posted: Mon Aug 04, 2008 9:13 am Post subject: |
|
|
.NET enables the link with other assemblies built using .NET, whatever the language. They all share a common base and conform to specification. With Win32 things are different as things can change between vendors. DLLs of course are a standard way of consuming others code and that is supported (without the need for a lib). |
|
Back to top |
|
|
DanRRight
Joined: 10 Mar 2008 Posts: 2818 Location: South Pole, Antarctica
|
Posted: Tue Aug 05, 2008 2:39 am Post subject: |
|
|
Thanks, got it. By chance, do you or anyone here who used Intel Fortran, knows is it possible to rebuid IVF static lib into IVF dll and will it work with ftn95?
By the way is dll succeptible to viruses same way like exe is? |
|
Back to top |
|
|
Andrew
Joined: 09 Sep 2004 Posts: 232 Location: Frankfurt, Germany
|
Posted: Sun Aug 17, 2008 10:30 am Post subject: |
|
|
I dont see why any code recompiled into a Win32 DLL with the appropriate entry points cannot be used with FTN95.
With viruses - its possible that any file can be affected really, there are all sorts of potential tricks with code injection etc. Any virus needs to be activated too mind you - so it needs to run at some point, which ultimately needs an executable of course. |
|
Back to top |
|
|
DanRRight
Joined: 10 Mar 2008 Posts: 2818 Location: South Pole, Antarctica
|
Posted: Sun Aug 17, 2008 11:37 am Post subject: |
|
|
Thanks Andrew, this is also confirmed by Intel' Steve Lionel. |
|
Back to top |
|
|
|