Hello!
This dialog window arises when I try to build a console project VS2017 15.9.7 XS2.0.0.9
followed by another on (see attachment).
Error list is empty,
Output is this:
" XSharp Compilation time: 00:08:22.2190926
Done building project "Prim.xsproj" -- FAILED.
0 Warning(s), 0 Error(s)
Build FAILED.
========== Build: 0 succeeded or up-to-date, 1 failed, 0 skipped =========="
Project attacked, too.
How can this be avoided?
SORRY, wrong forum
Can it be moved?
BR Kurt
XSCompiler.exe - System Warn... "Unknown Hard Error"
XSCompiler.exe - System Warn... "Unknown Hard Error"
- Attachments
-
- Prim_errorwindows.rtf
- (498.66 KiB) Downloaded 171 times
-
- prim.zip
- (12.07 KiB) Downloaded 167 times
XSCompiler.exe - System Warn... "Unknown Hard Error"
Hi Kurt,
It's a compiler bug, an internal error happens when it tries to compile this line:
Notice the missing "()" from the first "tostring" call, add the parens and it will compile fine. Will log this problem for Robert to look into (so the compiler reports an error instead of crashing) , thanks for your report!
It's a compiler bug, an internal error happens when it tries to compile this line:
Code: Select all
console.WriteLine(uiInx:tostring + ": " + uiprim1[uiInx]:ToString() + " --- " + uiPrim2[uiInx]:Tostring())
Chris Pyrgas
XSharp Development Team
chris(at)xsharp.eu
XSharp Development Team
chris(at)xsharp.eu
XSCompiler.exe - System Warn... "Unknown Hard Error"
Hi Chris,
FWIW, VB.NET allows ToString() without parenthesis. C# complains about at compile time.
If X# is going to handle it like C#, which I think it should, a compile time error should be reported like you said.
Jamal
FWIW, VB.NET allows ToString() without parenthesis. C# complains about at compile time.
If X# is going to handle it like C#, which I think it should, a compile time error should be reported like you said.
Jamal
- lumberjack
- Posts: 726
- Joined: Fri Sep 25, 2015 3:11 pm
- Location: South Africa
XSCompiler.exe - System Warn... "Unknown Hard Error"
I agree, compile time Error, ToString should be handled as a Property, hence no such property exist to be thrown as error.Jamal wrote: FWIW, VB.NET allows ToString() without parenthesis. C# complains about at compile time.
If X# is going to handle it like C#, which I think it should, a compile time error should be reported like you said.
My 2c.
______________________
Johan Nel
Boshof, South Africa
Johan Nel
Boshof, South Africa
XSCompiler.exe - System Warn... "Unknown Hard Error"
Hi Jamal,
Chris
Yeah, absolutely! Btw, I just realized that I had already logged this issue last week and Robert I think has already fixed it! Somebody had reported it last week already, but I managed to forget thatJamal wrote:Hi Chris,
FWIW, VB.NET allows ToString() without parenthesis. C# complains about at compile time.
If X# is going to handle it like C#, which I think it should, a compile time error should be reported like you said.
Jamal
Chris
Chris Pyrgas
XSharp Development Team
chris(at)xsharp.eu
XSharp Development Team
chris(at)xsharp.eu
XSCompiler.exe - System Warn... "Unknown Hard Error"
Chris,
This is new for me. But I'll fix it anyway.
Robert
This is new for me. But I'll fix it anyway.
Robert
XSharp Development Team
The Netherlands
robert@xsharp.eu
The Netherlands
robert@xsharp.eu
XSCompiler.exe - System Warn... "Unknown Hard Error"
Chris,
I just "wrote along" and as the error occurred I didn't change anything, because such errors may be hard to reproduce. Glad it helped to find it
BR Kurt
I just "wrote along" and as the error occurred I didn't change anything, because such errors may be hard to reproduce. Glad it helped to find it
BR Kurt
XSCompiler.exe - System Warn... "Unknown Hard Error"
I think is the same issue with Trim() without parenthesis we discussed last week.
George
George
XSCompiler.exe - System Warn... "Unknown Hard Error"
George,
Yes and it is fixed in our internal build.
Robert
Yes and it is fixed in our internal build.
Robert
XSharp Development Team
The Netherlands
robert@xsharp.eu
The Netherlands
robert@xsharp.eu
XSCompiler.exe - System Warn... "Unknown Hard Error"
Thank you Robert
George
George