Strange debugger behavior
John Esak
john at valar.com
Sun Oct 1 16:06:04 PDT 2006
The debugger did not handle @sk values at that version of filePro...
upgrading to a more current level will fix the problem. That is the only
solution I am aware of for debugging @sk code.
John
-----Original Message-----
From: filepro-list-bounces+john=valar.com at lists.celestial.com
[mailto:filepro-list-bounces+john=valar.com at lists.celestial.com]On Behalf Of
Tom Carey
Sent: Sunday, October 01, 2006 4:37 PM
To: filepro-list at lists.celestial.com
Subject: Strange debugger behavior
I'm reasonably new to FP. Working on 4.05.07 DOS ( dont' ask).
I find that the debugger seems to do things that I don't expect. I have a
series of statements on a @wlf that check the @SK to see if it was an ENTR
or SAVE key and branch off to different routines based on the key stroke and
other combined conditions.
If I single step thru the code, the first line correctly tests the @SK.
Subsequent lines don't seem to preserve the @SK correctly, so the test for
a SAVE key does not show as true. I am using the "S" key to single step thru
the code.
I have used show statements to prove that the first line of code is
correctly testing the @SK. And I did figure out that the show"@\...."
required a keystroke to clear the message and that entered a new key stroke
into the @SK vlaue. So I quit doing that.
Does the "S" keystroke used to single step replace the @SK value?
If I single step thru this code I wind up in different code than I do when
I execute it without the debugger.
Thanks
Tom Carey
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.celestial.com/pipermail/filepro-list/attachments/20061001/dc2d7052/attachment.html
More information about the Filepro-list
mailing list