Example of code with pointer warning:
Code: Select all
Sub s ()
End Sub
Dim As Integer Ptr p = @s
Print p
Sleep
Code: Select all
Sub s ()
End Sub
Dim As Integer Ptr p = @s
Print p
Sleep
Hi fxm,fxm wrote:Just a small remark:
When compiling with warning(s), the "Compiler Results" window is not displayed (only displayed when there is no warning).
Is this wanted?
Code: Select all
Sub s ()
End Sub
Dim As Integer Ptr p = @s
Print p
Sleep
Thanks cliff, yes my parsing for the error message did not take into account embedded parenthesis in the file name. Thanks for pointing that out - I will try to get a fix for the next update.cliff wrote:Hi there, I've noticed a minor bug with the Compiler Results tab in the Output Window at the bottom of the main WinFBE window. If the path to the .bas file being compiled includes a left parenthesis, the Line and File fields will contain incorrect information when the program contains errors. For example, make a new file named "example (text).bas", write a line of code that will cause an error, compile, then check the Compiler Results tab. Then try again with the file named "example (text.bas".
What suprises me (with 'Quick Run' or 'Build And Execute' menu) is that:PaulSquires wrote:When the "Hide successful compile results message" option is Unchecked, then the popup MessageBox will only display if there are if there are zero warnings and zero errors. If there is only warnings, then the messagebox will not display but the "Compiler Results" listview will display *and* the resulting EXE will be created and executed.
Ah, yes, right you are. I will modify the code so that the popup messagebox *will show* in cases where only warnings exist (because technically in WinFBE's view, a compile with only warnings is "successful").fxm wrote:- when there is no error neither warning, the user must click on the popup MessageBox to execute the program (pause if compile is perfect),
- when there is warning(s) the program starts immediately (no pause while there is compile warning).
I agree. I have changed the English wording. All non-English language files will need to be modified as well.I would intuitively prefer simply a "Hidesuccessfulcompile results message (popup)" option.
FB produces so many useless warnings (see this thread) that it would be nice to let the user decide if he wants to see the popup all the time or not.PaulSquires wrote:... so that the popup messagebox *will show* in cases where only warnings exist
WinFBE already has an option that allows you to never show the popup compile messagebox (regardless of whether there are warnings, errors, or any combination thereof).jj2007 wrote:FB produces so many useless warnings (see this thread) that it would be nice to let the user decide if he wants to see the popup all the time or not.PaulSquires wrote:... so that the popup messagebox *will show* in cases where only warnings exist
I didn't check - it would not occur to me. Yep, 26 June 2018 changelog.txt. I had a failed delivery from Amazon last week and had to sign an affidavit to get a replacement and now this. If I was younger I'd say "I need a drink". Actually, I still say it but with the medication that I am on, I am not allowed to. <laugh>PaulSquires wrote:although it does look like I failed to transfer the latest compiler and GCC 8.1