debug and release mod files

[martymike]

is it necessary to keep separate release and debug versions of the *.mod files?

[Jugoslav_Dujic]

No, it's not, although it's usually a practical thing to do; depends on what you have in mind.

Actually, it's quite likely that debug and release versions of the *mod files are bit-by-bit identical (except the short header containing the timestamp), provided that general settings are the same for both configuratons. As far as I can tell, VF's .mod files contain only information regarding variable declarations, initializers and parameter values, and routine interfaces.

There is a potential use of .mod files to also contain code for module procedures suitable for "inlining", but I'm not sure if VF utilizes it (Steve?) -- even if it does, it would be pretty wise to ensure that the mechanism doesn't break if a release .mod file is used in a debug configuration of another project.

[Steven_L_Intel1]

There's no code in a .mod - just declarations. I'm not aware of any differences in .mod files based on debug settings.

[martymike]

Thanks. We've always kept them separate, just to be careful. But for libraries that are shared by several products it would be simpler to not have to worry about that. That's what I'm going to do, now. Thanks, again.