dbTalk Databases Forums  

D3 debugging question

comp.databases.pick comp.databases.pick


Discuss D3 debugging question in the comp.databases.pick forum.



Reply
 
Thread Tools Display Modes
  #11  
Old   
Tony Gravagno
 
Posts: n/a

Default Re: D3 debugging question - 10-18-2005 , 10:34 PM






Bob Little wrote:
Quote:
The only problem is that the D3 debugger shows the line you have *just*
executed, and by that time, you are already into the subroutine.
It would be more useful if the D3 debugger (which I hate) would show you
the line you were *about* to execute.
One-stepping through debug isn't done in a vacuum. That is, your
knowledge of the program isn't completely limited to the one line you
happen to be looking at. If you're on line 105, use a command like
L90-115 to see the lines above and below where you are. You will
easily see all of the lines about to be executed after 105. If you
don't want do do that, open the program source in ED, WED, UP, VI, or
any other editor, or print a hardcopy.

Lighten up guys. These tools aren't perfect but we've been
workingwith them for 20-odd years and they probably aren't going to
change much - get use to them already.

For reference, if you're using AccuTerm it's very convenient if your
keyboard is programmed with UPdate processor key sequences (see
PickSource.com for a keymap). So ctrl-n is replaced logically with
the down-arrow and ctrl-j is replaced with a left-arrow (logical for
UPdate, not so much for ED).

T


Reply With Quote
  #12  
Old   
Bob Little
 
Posts: n/a

Default Re: D3 debugging question - 10-19-2005 , 10:56 AM






Tony Gravagno wrote:
Quote:
Bob Little wrote:

The only problem is that the D3 debugger shows the line you have *just*
executed, and by that time, you are already into the subroutine.
It would be more useful if the D3 debugger (which I hate) would show you
the line you were *about* to execute.


One-stepping through debug isn't done in a vacuum. That is, your
knowledge of the program isn't completely limited to the one line you
happen to be looking at. If you're on line 105, use a command like
L90-115 to see the lines above and below where you are. You will
easily see all of the lines about to be executed after 105.

Yes, I know. Extra steps though. My point is that if the Ultimate
Basic debugger (both during the Ultimate OS period and the UltPlus days)
did what I mentioned back in the 80s, why can't D3 do it now?

Quote:
Lighten up guys. These tools aren't perfect but we've been
workingwith them for 20-odd years and they probably aren't going to
change much - get use to them already.

I *was* used to it, I guess that's the problem. I tend to resist change
sometimes - even if it's a change for the worse. Go figure.

--
Bob Little
Graphik Dimensions, Ltd.
High Point, NC


Reply With Quote
  #13  
Old   
Bob Little
 
Posts: n/a

Default Re: D3 debugging question - 10-19-2005 , 04:00 PM



Glen B wrote:
Quote:
Small world, I'm in Wilmington, NC. :P

Glen
Wilmington is a cool place. Unless there's a Rita or an Isabel coming
to visit.


--
Bob Little
Graphik Dimensions, Ltd.
High Point, NC


Reply With Quote
  #14  
Old   
Tony Gravagno
 
Posts: n/a

Default Re: D3 debugging question - 10-19-2005 , 04:06 PM



Bob Little wrote:
Quote:
My point is that if the Ultimate
Basic debugger (both during the Ultimate OS period and the UltPlus days)
did what I mentioned back in the 80s, why can't D3 do it now?
The development teams for these platforms were different, the market
demand was different, and back in the 80's when Ultimate was big there
was much more incentive for a licensee to differentiate. These days
there are no licensees and the market prefers to make demands in
public forums rather than asking the vendor directly for changes.
Even if action items were filed with RD now, I doubt that major
changes would be made to the BASIC debugger, it's not the sort of
change that will bring in new income. (I can feel people stirring in
their seats but that's the world we live in.)

Quote:
I *was* used to it, I guess that's the problem. I tend to resist change
sometimes - even if it's a change for the worse. Go figure.
I'm a creature of habit in many ways too - in this case we've had
about 15 years to acclimate ... hardly unreasonable.

Looking at this thread an idea was refreshed that I haven't had in a
long time. I don't think it would be amazingly hard to write a GUI
front-end to the debugger which showed a normal screen in one pane and
debugger status in another, with variables, code lines, etc. It's
just a matter of knowing when to turn on/off screen capture and then
displaying the right pieces in the right pane. Unfortunately I doubt
anyone would pay for such a thing, and here we are again with
innovation in our market being stiffled because people will insist on
everything being free. Now I remember why I forgot about this in the
first place.

T


Reply With Quote
  #15  
Old   
Luke Webber
 
Posts: n/a

Default Re: D3 debugging question - 10-19-2005 , 06:11 PM



Bob Little wrote:

Quote:
Yes, I know. Extra steps though. My point is that if the Ultimate
Basic debugger (both during the Ultimate OS period and the UltPlus days)
did what I mentioned back in the 80s, why can't D3 do it now?
We need Chandru in on this thread, because he had a part in the rewrite
of the Ultimate debugger. David Rose also played a large role.

Luke


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.