PureBasic Forums - English

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?

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

> Many people (including Fred) have the error log hidden all the time...
maybe he should unhide it. sorry, i couldnt resist.

c ya,
nco2k

nco2k wrote:> Many people (including Fred) have the error log hidden all the time...
maybe he should unhide it. sorry, i couldnt resist.

c ya,
nco2k

What do you think i am telling him all the time?

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

Lol, but when we start to use the new commands and don't compile old sources often. Will there be an option then?

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.

Please get rid of this. Errors are more important than warnings, so it does not make sense to have a more annoying windows for warnings than for errors.

Also, I just don't like it. And I have the error log open.

IMHO one window would do for all output, i.e. Errors, Warnings and Debug output! By default show it when something is written to it.

> Also, I just don't like it

Now that's a compelling reason to change it!

I like that idea Kale,
but while at it. why not combine the behavior of the two.
A single error/log/warning window, with docked and undocked option.
With auto show/hide until first error etc.

*looks at freak* try it for Beta2 if there's enough time?

For me one window will do and have a settings which you can check if you want to see warnings, etc.

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)

I'd rather have it added to the Debug window, strange as it may sound.

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.

The Debug window is for the app's runtime messages, not for the compiler.
Having compiler error messages or warnings in it defeats its entire concept.

i just think it will be cleaner to have a generic 'Output' window for all messges. And errors and warnings can not be turned off.

The last thing I want to do when looking at my app's debug commands is sort
through any compiler messages mixed in my app's data. Surely you'd agree?