topic DLLEXPORT attributes in Software Archive

DLLEXPORT attributes

Intel_C_Intel — Fri, 27 Apr 2001 00:35:30 GMT

This is more of a curiosity/FYI, our legacy FPS code has several external DLL attributes specified as

!MS$ATTRIBUTES DLLEXPORT :: msgetinp
!MS$ATTRIBUTES ALIAS : 'getinp' :: msgetinp

and they compile and function on the CVF compiler. I've changed them to

!DEC$ATTRIBUTES DLLEXPORT :: msgetinp
!DEC$ATTRIBUTES ALIAS : 'getinp' :: msgetinp

but I was wondering if the compiler was designed to be this smart for the FPS upgrade, or is this a missed warning?

Re: DLLEXPORT attributes

Intel_C_Intel — Fri, 27 Apr 2001 01:04:54 GMT

http://www.compaq.com/fortran/visual/prod-desc.html has a long list of supported FPS extensions including those in your post:

!MS$ metacommand Form

$ATTRIBUTES ALIAS-external name for a subprogram or common block

$ATTRIBUTES DLLIMPORT, DLLEXPORT-import/export from DLL

hth,
John

Re: DLLEXPORT attributes

Steven_L_Intel1 — Fri, 27 Apr 2001 01:57:49 GMT

We have tried, wherever reasonable (and some places not so reasonable) to accept documented MS PowerStation 4.0 syntax, including directives. The idea was that DVF (now CVF) would be a "drop-in replacement" for PowerStation 4.0.

We came so close to this that many people believe, to this day, that we simply took Microsoft's compiler and modified it! There are a few MS-isms we don't support, such as $DEBUG and file-scope INTERFACE blocks. Note that we even support the INTERFACE TO syntax from PowerStation 1 that FPS4 didn't document (but which was widely used by FPS4 customers.)

Steve