Re: breakpoint in dbase 4 ver 2 (DOS)

In article <oTpebPPYIHA.464@news-server>, fred@polyflexseals.co.za 
says...
> Ok here is some feedback--
> 
> debug on its own line is not allowed by the complier so it wont
> compile and I think it will want to start at the beginning of the program
> sorry Geoff
> 
> "set step on" is a help but noway to check the values of
vars,etc
> 
> The debugger screen would be first prize!!
>

Relying on an increasingly creaky memory.  I think I used to do 
something nonsensical like: 

? x

where x was undefined at the point I wanted to invoke the debugger.  
When the program reached that point, debug was one of the options.  But 
that's from memory, so......

-- 
Marilyn Price

Thanks everybody-- will try the "debug" first and report back
regards fred


"Fred Evans" <fred@polyflexseals.co.za> wrote in message
news:QR3e%23ncXIHA.940@news-server...
> I am writing some code in dbase 4 ver 4 ( Vintage about 1998 )
>
> does anyone know how to start the Debugger from with-in the code?
>
> Example  ( I always use q=.t. as the flag for the debugger to stop)
>
> I start the proc as follows "Debug <myproc>"
>
> then I set the breakpoints in the debugger window.
> this is rather tedious and I would prefer to set up a flag similar to
> an error trap.
>
> Maybe something like "on q=.t. then debug "
>
> something that tests for the value of "Q" and enters the debugger
at that
> point
> I would initialize "Q=.f." at the beginning of the proc.
> then wherever I want the debugger to stop- I just put in the line
"q=.t."
>
> regards fred evans
>
>

On Sun, 27 Jan 2008 16:24:30 +0200, in dbase.how-to, 
Subject: Re: breakpoint in dbase 4 ver 2 (DOS), 
Message-ID: <oTpebPPYIHA.464@news-server>,  
"Fred Evans" <fred@polyflexseals.co.za> wrote:

>Ok here is some feedback--
>
>debug on its own line is not allowed by the complier so it wont
>compile and I think it will want to start at the beginning of the program
>sorry Geoff
>
>"set step on" is a help but noway to check the values of vars,etc
>
>The debugger screen would be first prize!!
>Any more suggestions

I suggested to use SET TRAP ON.

Did it not work?

Ok here is some feedback--

debug on its own line is not allowed by the complier so it wont
compile and I think it will want to start at the beginning of the program
sorry Geoff

"set step on" is a help but noway to check the values of vars,etc

The debugger screen would be first prize!!
Any more suggestions

"Fred Evans" <fred@polyflexseals.co.za> wrote in message
news:XIxj81MYIHA.1092@news-server...
> Thanks everybody-- will try the "debug" first and report back
> regards fred
>
>
> "Fred Evans" <fred@polyflexseals.co.za> wrote in message
> news:QR3e%23ncXIHA.940@news-server...
> > I am writing some code in dbase 4 ver 4 ( Vintage about 1998 )
> >
> > does anyone know how to start the Debugger from with-in the code?
> >
> > Example  ( I always use q=.t. as the flag for the debugger to stop)
> >
> > I start the proc as follows "Debug <myproc>"
> >
> > then I set the breakpoints in the debugger window.
> > this is rather tedious and I would prefer to set up a flag similar to
> > an error trap.
> >
> > Maybe something like "on q=.t. then debug "
> >
> > something that tests for the value of "Q" and enters the
debugger at
that
> > point
> > I would initialize "Q=.f." at the beginning of the proc.
> > then wherever I want the debugger to stop- I just put in the line
"q=.t."
> >
> > regards fred evans
> >
> >
>
>

Thanks Marilyn--

? x works like a charm

regards

fred


"Marilyn Price" <mprice@tri_con.net> wrote in message
news:MPG.22066f63ed30c5989753@news.dbase.com...
> In article <oTpebPPYIHA.464@news-server>, fred@polyflexseals.co.za
> says...
> > Ok here is some feedback--
> >
> > debug on its own line is not allowed by the complier so it wont
> > compile and I think it will want to start at the beginning of the
program
> > sorry Geoff
> >
> > "set step on" is a help but noway to check the values of
vars,etc
> >
> > The debugger screen would be first prize!!
> >
>
> Relying on an increasingly creaky memory.  I think I used to do
> something nonsensical like:
>
> ? x
>
> where x was undefined at the point I wanted to invoke the debugger.
> When the program reached that point, debug was one of the options.  But
> that's from memory, so......
>
> -- 
> Marilyn Price
> M. P. Data