#NULL wrote:I can now run that code with analyzer.
Same here. Thank you for the update!
Unfortunately, now I'm encountering another issue.
When running this small demo program (with PB 5.70 beta 4 on Windows 10)
Code: Select all
XIncludeFile #PB_Compiler_Home + "..\libs\string.pbi"
x = 3
then I get this result
Analyzer 3.2 For PB570
loading preferences : C:\Users\LJ\Desktop\Analyzer\analyzer.ini
file : C:\Users\LJ\AppData\Local\Temp\PB_EditorOutput.pb
compile/run with analyzer?
[Continue]
mainfile : C:\Users\LJ\Desktop\analyzer_test.pb
base include path : C:\Users\LJ\Desktop\
merging include files..
mergeTool
------------
mainfile : C:\Users\LJ\AppData\Local\Temp\PB_EditorOutput.pb
orig. file : C:\Users\LJ\Desktop\analyzer_test.pb
baseIncPath : C:\Users\LJ\Desktop\
------------
fileName : C:\Users\LJ\Desktop\PB_Compiler_Home + "..\libs\string.pbi
baseIncPath : C:\Users\LJ\Desktop\PB_Compiler_Home + "..\libs\
can't read file : C:\Users\LJ\Desktop\PB_Compiler_Home + "..\libs\string.pbi
failed to include file : C:\Users\LJ\Desktop\PB_Compiler_Home + "..\libs\string.pbi
------------
------------
merge failed.
merge failed. program will compile/run without analyzer.
The red paths are wrong, the compiler is located elsewhere. Additionally, the red paths contain only one (i.e. unbalanced) quote.
I also stumbled across another small issue.
Normally, I don't use
Code: Select all
XIncludeFile #PB_Compiler_Home + "..\libs\string.pbi"
as above, but
Code: Select all
XIncludeFile #PB_Compiler_Home + "../libs/string.pbi"
Using forward slashs, the code runs without modifications on Windows and Linux.
It seems that Analyzer doesn't like that on Windows. After changing the above code to
Code: Select all
XIncludeFile #PB_Compiler_Home + "../libs/string.pbi"
x = 3
I get this result
baseIncPath : C:\Users\LJ\Desktop\PB_Compiler_Home + "../libs/\
I don't know whether this causes a problem, or whether this is only a cosmetic issue in the output.