Tweet
There's a DLL that I'm working on. Occasionally, rather than
run a host program to call the DLL, I simply temporarily
change the directive in the DLL code itself to something like:
$Compile Exe "Test.Exe"
And then I replace the LibMain with PBMain and add a few lines
so I can run it like a program. If I change LibMain to PBMain
but forget the change the $Compile directive, then I get an
error message if I click on the Debugger, as I'd expect.
However, if I click on Build/Execute in order to run the program,
if Test.Exe exists in the directory, then it runs that one but
doesn't give an error for the $Compile DLL statement. It gives
the impression that the code on the screen is what's running,
when something else is really running.
------------------
Daniel Corbier
UCalc Fast Math Parser
http://www.ucalc.com
run a host program to call the DLL, I simply temporarily
change the directive in the DLL code itself to something like:
$Compile Exe "Test.Exe"
And then I replace the LibMain with PBMain and add a few lines
so I can run it like a program. If I change LibMain to PBMain
but forget the change the $Compile directive, then I get an
error message if I click on the Debugger, as I'd expect.
However, if I click on Build/Execute in order to run the program,
if Test.Exe exists in the directory, then it runs that one but
doesn't give an error for the $Compile DLL statement. It gives
the impression that the code on the screen is what's running,
when something else is really running.
------------------
Daniel Corbier
UCalc Fast Math Parser
http://www.ucalc.com
Comment