RE: A pain to compile from code editor?

Interesting.  I've had better luck from outside the CODE editor.  I'm going
to look at the manual. I'd like to believe the behavior I've seen is
predictable.  We need the old Borland stand alone debugger.  Besides the
features it shared with the IBM product, you could step backwards through a
program if you spaced out and missed the line of code you wanted to see.
(Not that I ever needed to use that. <g>)

> -----Original Message-----
> From: Buckingham, Ed [mailto:Buckingham@AE.com]
> Sent: Monday, March 25, 2002 1:53 PM
> To: 'code400-l@midrange.com'
> Subject: RE: A pain to compile from code editor?
>
>
> When I do use it, I use it in interactive mode and most times
> the program
> being debugged is a direct call to the program.  The way that
> I start the
> debugger is through the CODE 400 editor.  I make sure I get a
> clean compile
> and then hit the debug button on the menu bar at the top of
> the editor, not
> through the menu options.  Most times my program will start up in the
> debugging environment automatically.  If I try to get it
> going other ways
> then my results are not as reliable.  I liked the older
> version they had of
> the debugger.  It was faster and had mouse support for
> scrolling in the
> windows.  This debugger is still being used in the VARPG
> editor.  Just my
> two cents worth.
>
> > -----Original Message-----
> > From:       Joel Fritz [SMTP:JFritz@sharperimage.com]
> > Sent:       Monday, March 25, 2002 4:47 PM
> > To: 'code400-l@midrange.com'
> > Subject:    RE: A pain to compile from code editor?
> >
> > Hmm...you've gotten the "Cooperative" Debugger to work
> consistently?  I'd
> > given up on it. Maybe I need to read the manual.
> >
> > > -----Original Message-----
> > > From: Buckingham, Ed [mailto:Buckingham@AE.com]
> > > Sent: Monday, March 25, 2002 1:28 PM
> > > To: 'code400-l@midrange.com'
> > > Subject: RE: A pain to compile from code editor?
> > >
> > >
> > > I am not real sure on the Debug options.  I do know that they
> > > will save a
> > > profile for each program that is debugged.  I think they will
> > > keep the watch
> > > variables and a few other items so that you do not have to
> > > keep rekeying
> > > them, but I do not use it that often, unless I really need to
> > > put a program
> > > under the microscope.  For most of my debugging I use the
> green screen
> > > debugger.  It is just faster to go that route.  CODE 400's is
> > > very nice but
> > > I find it to be slow to start and get a quick check on parms
> > > being passed or
> > > variable or array values.  The main thing to remember is
> to exit the
> > > debugger through the drop down menus and not the "X" in the
> > > corner.  Seems
> > > to be the only way settings get saved.  Hope this helps!
> > >
> > _______________________________________________
> > This is the CODE/400 Discussion & Support (CODE400-L) mailing list
> > To post a message email: CODE400-L@midrange.com
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
> > or email: CODE400-L-request@midrange.com
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/code400-l.
> _______________________________________________
> This is the CODE/400 Discussion & Support (CODE400-L) mailing list
> To post a message email: CODE400-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
> or email: CODE400-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/code400-l.
>