Karl-Heinz wrote:Hi Chris,- i created a VS app with the same source code and the errors XS9002 and XS9111 are shown.- the same errors are shown when I compile the rsp file created by XIDE in the command prompt. i hope the content of both pngs are readable.so the question is: Why do i see inside XIDE the "compilation failed" error instead of the 2 errors ?regardsKarl-Heinz
I am as confused as you are...are you using any XIDE plugins?
...also, can you zip and send me the complete folder of the project where you have this test app? Maybe there's something in it that affects the way the app gets compiled. Can't think of something, but maybe seeing the project will reveal something...
Karl-Heinz,
Chris will have to answer this one.
But the 2 errors are what I would expect.
I have added the second error in this build to help people to diagnose errors that are UDC related.
Robert
XSharp Development Team
The Netherlands
robert@xsharp.eu
Attached is a newly created project that contains a single app. The content of this app is the known code that still fails with the error msg "compilation failed"
Thanks, it still works fine here! Is it possible that maybe you have XIDE pointing to an older compiler version, maybe for testing an older one? I mean in Preferences/Compiler.
Also what if you do a Project/Rebuild Project, does it make any difference?
If not, can you also send me the XIDE.cfg file? So I can try the exact same preferences that you are you using, also in my machine, maybe there's something in there causing this (although I still can't think of something).
Project/Rebuild makes no difference. Also a fresh installed XIDE makes no difference. I think the best is to visualize the problem. In the attached zip is a animated gif. Instead of the 'WAIT' command i'm using the Commands 'CLOSE' and 'CLOSE DATABASES'
Only 'CLOSE DATABASES' throws the errors XS9002 and XS9111, while 'CLOSE' throws the 'compilation error'
Aha, on a freshly installed XIDE, I also get the problem!! Let me check the options one by one, for some reason one of them is causing this it seems.
Or there's some other issue that should be debuggable now.
When i uncheck the "Show only one parser error per file" setting ( Preferences -> Tabpage "Compiler" ) the "compilation failed" is gone and the XS9002 and XS9111 are listed. i never noticed this setting before. Whats the reason why this setting exists ?
Ah great, good catch! The reason for this option was that in the past the X# compiler, when it was finding a syntax error, it would go out of sync and instead of reporting just this one error, it would also reports dozens more, caused by the first one, and that would just would just clutter the output, making it very hard to spot that single error that actually needed to be fixed (and by fixing it all the other parser errors went away).
So I added this option, which would only show the first parser error, that the compiler is reporting. Since then, the same logic has been applied to the compiler itself, so the XIDE option is now obsolete, I just left it in there just in case it is needed again in the future. But still, of course it should not cause such a problem with the compiler output, this is a bug. Will debug and fix it, thanks for all your help finding this out!
Edit: Found it, was a stupid mistake, I had hardcoded the error parsing code to search for files with a ".prg" extension, but in this case the error is happening in an include (.xh) file, which was causing that code to throw an exception, which would then abort all further error reporting. It's fixed now, implemented a better error message analyzing function.
