"Mixed" projects: compiling program units with different compile options and linking them

Several of my applications manipulate image data, consisting of arrays of single characters. For these applications, I don't use Checkmate because of the way it 'detects' undefined variables (using a specific byte value). For image data, this specific byte value is as good as any other, and so every time it occurs legitimately it generates a false positive runtime error - as a result, I build these apps with /debug as the highest diagnostic level. Unfortunately, this throws the baby out with the bathwater, where 'baby' = all the other stuff that Checkmate does, which I /would/ like to use - but it's all too easy to forget that I'm working without the Checkmate safety net.

I just got reminded of this when I had to track down a puzzling data overwrite which turned out to be due to a write past the end of an array - that Checkmate would have identified (I just checked, and it did, at runtime; however, before I even got that far, I got a compile-time warning that has got me worried about something else now - see separate post).

Which leads me to my question:

In principle, different program units could be compiled with different compile options, and linked to form an exe with different levels of diagnostic power in different parts. Assume I reorganise my code so that I separate out the parts where I need to forsake Checkmate as a compile option. I end up with program units that need to be compiled with different compile options, and then linked. Can I do this within Plato? If not, how would I go about it in a command line manner?

Andy

Plato applies the same compiler options to every file within a project, i.e. one set for Release, one for Debug and one for CheckMate.

One approach you might try is to use OPTIONS(CHECK) etc in the code together with conditional compilation code. You could then set the appropriate VPARAM (for example) in the project properties.

Otherwise you may end up writing a compile and link batch file to run from a DOS box.

I've made some progress on this now. I isolated the code that needs to be compiled as /DEBUG into a little separate module. I build the entire project as both /DEBUG and /CHECKMATE, and copy the object code for the module in question from \DEBUG\WIN32 TO \CHECKMATE\WIN32 (overwriting or renaming the original version). The problem is how to relink the revised object code without recompiling. At first I tried rebuilding the /CHECKMATE version from within Plato; I figured that if changed source code triggers recompilation and relinking, unchanged source code but changed object code might trigger relinking only. This worked the first few times - then it stopped working, with Plato insisting 'Target is up to date' and not invoking SLINK, so I wrote a batch file to do the job.

Q: how does Plato 'know' when recompilation and relinking are necessary i.e. why would my original approach work sometimes, but not consistently?

Andy

The next release of Plato has an improved method for testing when to compile and when to link. Currently you get a recompile and relink for almost any change to the project properties. In the next release the properties are classified as to whether they require a recompile, or a relink or neither.

I do not know why you are get an inconsistent behaviour but hopefully everything will be OK in the next release.

Good news. It seems I am pushing on an open door - is that the right figure of speech? Thanks.