Jump to line number on error

Got an idea for enhancing PureBasic? New command(s) you'd like to see?
PB
PureBasic Expert
PureBasic Expert
Posts: 7581
Joined: Fri Apr 25, 2003 5:24 pm

Jump to line number on error

Post by PB »

When the Debugger highlights an error line in red, and I click "Quit" to get rid
of the Debugger, it would be nice if the IDE could jump to that line number, to
make getting to the problem easier. At the moment I have to take note of the
line number and then do CTRL+G and enter the line number manually. :(
I compile using 5.31 (x86) on Win 7 Ultimate (64-bit).
"PureBasic won't be object oriented, period" - Fred.
freak
PureBasic Team
PureBasic Team
Posts: 5940
Joined: Fri Apr 25, 2003 5:21 pm
Location: Germany

Post by freak »

You are using the external debugger ?
Because the internal one shows the error directly hilights the line in the IDE, so there is no need to search.

I will check if i can add it to the external one as well.
quidquid Latine dictum sit altum videtur
PB
PureBasic Expert
PureBasic Expert
Posts: 7581
Joined: Fri Apr 25, 2003 5:24 pm

Post by PB »

Hi Freak, yes, I prefer using the Standalone GUI Debugger.

As a side-note, why are there 2 debuggers anyway? How different are they,
and are there any advantages in using one versus the other at any time?
I compile using 5.31 (x86) on Win 7 Ultimate (64-bit).
"PureBasic won't be object oriented, period" - Fred.
freak
PureBasic Team
PureBasic Team
Posts: 5940
Joined: Fri Apr 25, 2003 5:21 pm
Location: Germany

Post by freak »

When i rewrote the debugger, the one included in the IDE was supposed to be the
new way of debugging in PB.

The standalone one was only created to not kill off jaPBe or the possibility to
use any other 3rd party editor, because they would have been limited
to the console only debugging then.

The two debuggers share most of their codebase. The difference is only in the
way the sourcecode, errors, breakpoints and such are presented. The
debugging tools are the same.
(except the CPU monitor which is only present in the IDE)

The integrated debugger has the advantage of not adding another window (which again displays the same sourcecode).
Also stuff like breakpoints is more comfortable there, as they stay between debugging sessions for example.

The standalone one has the advantage that the sourcecode is not locked while you
run a debug-session, so you can continue editing in the IDE if you want.

Both have their uses, although the differences are not that big.
Thats why there is a choise... ;)
quidquid Latine dictum sit altum videtur
Post Reply