PureBasic Forums - English

Please take out the 'pop up' and replace it with the same type of behaviour as a regular error, ie. 'ping' plus marked line plus note at the bottom of the window.

The different behaviour is a bit annoying and slows one down, IMHO disclaimers etc. etc.

I am assuming you mean the error you get when you don't declare a variable with EnableExplicit ?

This is a compiler error and is handled like all other compiler errors. (Syntax error etc.)
What you mean i think are debugger errors. (Division by zero etc)

Yep, that's what I meant

Let me rephrase it: it would be nice if it would be reported in the same way as a debugger error

Well, but its a compiler error, not a debugger one. Why treat this one error differently ?

Because it's more comfortable when editing, as it is one of the most frequently occuring errors when using EnbleExplicit.

I think it would just lead to confusion. Its a compiler error, so it has to act like one.
Debugger errors are very different, as then you can examine the program state with the debugger tools etc. You cannot do that after a compiler error.

what about an option in the preferences to switch compiler errors from MsgBox to DebugLine?

Kaeru Gaman wrote:what about an option in the preferences to switch compiler errors from MsgBox to DebugLine?

Oh yessssssss ! I second that !!!
Great, great suggestion.

And it wouldn't take any functionality away, now, would it ?
We'd still know without a doubt that something needs to be corrected since the compiler would stop dead in its tracks, exactly as it does now, but without the extra click... It's that click (and the unavoidable ding that precedes it...) that I personnally would like to do without.

Yes!

+32768!