Editor - EnableExplicit error message

Got an idea for enhancing PureBasic? New command(s) you'd like to see?
User avatar
blueznl
PureBasic Expert
PureBasic Expert
Posts: 6166
Joined: Sat May 17, 2003 11:31 am
Contact:

Editor - EnableExplicit error message

Post by blueznl »

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. :-)
( 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... )
freak
PureBasic Team
PureBasic Team
Posts: 5940
Joined: Fri Apr 25, 2003 5:21 pm
Location: Germany

Post by freak »

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)
quidquid Latine dictum sit altum videtur
User avatar
blueznl
PureBasic Expert
PureBasic Expert
Posts: 6166
Joined: Sat May 17, 2003 11:31 am
Contact:

Post by blueznl »

Yep, that's what I meant :oops:

Let me rephrase it: it would be nice if it would be reported in the same way as a debugger error :P
( 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... )
freak
PureBasic Team
PureBasic Team
Posts: 5940
Joined: Fri Apr 25, 2003 5:21 pm
Location: Germany

Post by freak »

Well, but its a compiler error, not a debugger one. Why treat this one error differently ?
quidquid Latine dictum sit altum videtur
User avatar
blueznl
PureBasic Expert
PureBasic Expert
Posts: 6166
Joined: Sat May 17, 2003 11:31 am
Contact:

Post by blueznl »

Because it's more comfortable when editing, as it is one of the most frequently occuring errors when using EnbleExplicit.
( 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... )
freak
PureBasic Team
PureBasic Team
Posts: 5940
Joined: Fri Apr 25, 2003 5:21 pm
Location: Germany

Post by freak »

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.
quidquid Latine dictum sit altum videtur
User avatar
Kaeru Gaman
Addict
Addict
Posts: 4826
Joined: Sun Mar 19, 2006 1:57 pm
Location: Germany

Post by Kaeru Gaman »

what about an option in the preferences to switch compiler errors from MsgBox to DebugLine?
oh... and have a nice day.
User avatar
Blue
Addict
Addict
Posts: 964
Joined: Fri Oct 06, 2006 4:41 am
Location: Canada

Post by Blue »

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.
Last edited by Blue on Sat Jul 05, 2008 8:10 pm, edited 2 times in total.
PB Forums : Proof positive that 2 heads (or more...) are better than one :idea:
User avatar
blueznl
PureBasic Expert
PureBasic Expert
Posts: 6166
Joined: Sat May 17, 2003 11:31 am
Contact:

Post by blueznl »

Yes!

+32768!
( 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... )
Post Reply