keyword SAVE and DLLs

keyword SAVE and DLLs

This is a general question, with some specific implimentations.  I am building a fortran DLL that will be part of a much larger program (written in C++ and C#).  I want to retain some of the varaibles internally without having to re-compute them.  If I was building the program all myself I would simply use the 'SAVE' keyword.  Will that still work across the DLL interface?  I don't want my data to get corrupted without me knowing it.  And in a similar situation, if the variable I am 'SAVE'ing is allocatable?  Will it maintain its allocated nature and the data?  This is something I need to be sure about.

2 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

If you're talking about calls to DLL routines from the same program run, then yes, SAVE is what you want. In this context it is no different from a static library. Yes, if you SAVE an ALLOCATABLE it will persist across calls.

Retired 12/31/2016

Leave a Comment

Please sign in to add a comment. Not a member? Join today