Is there any need for another compiler warnings window?

[Kale]

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?

If your program is written correctly you shouldn't have any compiler messages.

[maw]

If your program is written correctly you shouldn't have any compiler messages.

If your program is written correctly you shouldn't have any compiler warnings, alas, this thread is meaningless..

Personally, I like the warning window. I tells me in no uncertain terms that I haven't updated my code to the new standard yet.

[PB]

> If your program is written correctly you shouldn't have any compiler messages

Har. Har. Har.

[CSAUER]

Back to topic:

What about a option inside IDE preferences to select one of the warning outputs:
- send warnings to error log
- send warnings to debug window
- send warnings to separate window (maybe pre-defined)

You would match all interests.

Best Regards

CSAUER

[Trond]

> 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.

- No, I can't ignore it even if I want to.
- If I move it out of the screen it just pops back in. It will not stay out of the way.
- To close the error requester I can just hit enter, to close the warnings window I need to minimize my own program, close the window and the restore my own program.

[Trond]

Also, the warnings are already put in the error log, I don't see why they should be shown twice.

[Trond]

And even if I select "ignore warnings" they are still shown twice...

[freak]

And even if I select "ignore warnings" they are still shown twice...

This is for the debugger warnings.

Just adjust your code and the warnings will be gone.

[Trond]

I can't adjust my code because it's a template, and they are shared between 4.20 and 4.30 beta.

If I change the code I can't use the template with 4.20 any more, and also I'd have to put the warning-producing code back in before posting it at the forum (as I do not want to unnecessarily post code that only works in the beta version).

[Justin]

So after almost 10 years isn't still a way to hide this annoying warning window?
I have a code like this:

Code: Select all

ProcedureDLL foo(Array arr.s(1))
	
EndProcedure

the procedure fills the array and works perfectly, but the annoying warning window pops up saying it can cause issues, what kind of issues? can i use it or not?
the warnings already appear in the error output, there is no need for this.