Is there any need for another compiler warnings window?
Is there any need for another compiler warnings window?
Is there any need for another compiler warnings window?
I just wondered if the compiler warnings could output to the debug output window instead. Maybe make this a preference?
I just wondered if the compiler warnings could output to the debug output window instead. Maybe make this a preference?
Many people (including Fred) have the error log hidden all the time, so they would never notice any warnings.
The warnings window remembers its position. So just move it somewhere to the edge of the screen and it will stay out of the way.
There is no setting to get rid of the window, because you are not supposed to just ignore these warnings. You should fix the warned-about functions and the warnings will go away
The warnings window remembers its position. So just move it somewhere to the edge of the screen and it will stay out of the way.
There is no setting to get rid of the window, because you are not supposed to just ignore these warnings. You should fix the warned-about functions and the warnings will go away
quidquid Latine dictum sit altum videtur
Lol, but when we start to use the new commands and don't compile old sources often. Will there be an option then?freak wrote:There is no setting to get rid of the window, because you are not supposed to just ignore these warnings. You should fix the warned-about functions and the warnings will go away
Or, have the error log open itself if there is an error and stay hidden if there is no error? It just seems a bit redundant to have lots of different unconnected windows open when one would do.
For me one window will do and have a settings which you can check if you want to see warnings, etc.
something like
something like
C:\sample\sample.pb(40) : error #: Error msg.
C:\sample\sample.pb(73) : warning #: Warning msg.
sample.exe - 1 error(s), 1 warning(s)
[Registered PB User since 2006]
[PureBasic 5.7][SpiderBasic 2.2] [Win 10 64bit]
[Intel i7 990x 4.20 Ghz] [18GB DDR3]
I'd rather have it added to the Debug window, strange as it may sound.
( PB6.00 LTS Win11 x64 Asrock AB350 Pro4 Ryzen 5 3600 32GB GTX1060 6GB)
( The path to enlightenment and the PureBasic Survival Guide right here... )
( The path to enlightenment and the PureBasic Survival Guide right here... )
So these are the options now?
- send warnings to error log
- send warnings to debug window
- send warnings to separate window
- send warnings to outer space
- send warnings to Bill Gates
- all of the above
I still see the current one as a good solution.
Remember, the purpose of the warnings is to be visible. If you do not notice them, they do not serve any purpose.
The log contains compiler errors as well as all debugger log messages. I think the compiler warnings would simply go unnoticed there, as there is no additional feedback like on a compiler error (Requester and compilation abort)
> Errors are more important than warnings, so it does not make sense to have a more annoying windows for warnings than for errors.
A compiler error opens a requester. You have to confirm it before doing anything else. The compiler warning window does not stop compilation or execution of the program. You can just ignore it if you want to. Plus: if you move it out of the way, it will stay out of the way the next time unlike a requester. Thats much less annoying in my book.
- send warnings to error log
- send warnings to debug window
- send warnings to separate window
- send warnings to outer space
- send warnings to Bill Gates
- all of the above
I still see the current one as a good solution.
Remember, the purpose of the warnings is to be visible. If you do not notice them, they do not serve any purpose.
The log contains compiler errors as well as all debugger log messages. I think the compiler warnings would simply go unnoticed there, as there is no additional feedback like on a compiler error (Requester and compilation abort)
> Errors are more important than warnings, so it does not make sense to have a more annoying windows for warnings than for errors.
A compiler error opens a requester. You have to confirm it before doing anything else. The compiler warning window does not stop compilation or execution of the program. You can just ignore it if you want to. Plus: if you move it out of the way, it will stay out of the way the next time unlike a requester. Thats much less annoying in my book.
quidquid Latine dictum sit altum videtur