WHAT:
At minimum for a specific build, better yet for a specific source, better yet with a compiler directive for a specific portion of code.
At minimum for all warnings, better yet for a specific warning (probably this would require the ability to identify a warning with a number or mnemonic constants, not a bad idea generally speaking).
WHY:
To disable the emission of warnings well known and accepted, and consequently to avoid to pay attention to the warnings popup window to check the list to see if there is some specific new warning not intended, and also to avoid the click on the close button at every compilation.
A way to disable compiler warnings
A way to disable compiler warnings
"Have you tried turning it off and on again ?"
A little PureBasic review
A little PureBasic review
Re: [Implemented] A way to disable compiler warnings
Just noticed this has been modified to [Implemented].
Thank you obviously, but do you mean for the next version or I missed this in 5.11 ?
I tried to look around in the settings but it seems all as usual, I'm not sure when this thing happened.
Anyone know something about it ?
Thank you obviously, but do you mean for the next version or I missed this in 5.11 ?
I tried to look around in the settings but it seems all as usual, I'm not sure when this thing happened.
Anyone know something about it ?
"Have you tried turning it off and on again ?"
A little PureBasic review
A little PureBasic review
Re: [Implemented] A way to disable compiler warnings
Still don't see this implemented in 5.20B1.
Are you sure this [implemented] was not put here in error ?
Are you sure this [implemented] was not put here in error ?
"Have you tried turning it off and on again ?"
A little PureBasic review
A little PureBasic review
Re: A way to disable compiler warnings
Seems to be by mistake, yes.