> - added script debugging support through exec.scriptdebug
>
This is great, a big step forward for scripters, thank you.
Some problems in this first cut.
I added exec.scriptdebug(1) to a script and ran it:
1. the initial line count was wrong (smaller that it should have been). I thought it could be due to wrong
count of comment lines, but that turned out not to be the cause
2. run to ;b! appears to run only to the end of the current label if no ;b! is found before QUIT
3. ghost label? I have a script that starts with ;quit( ... ) and the debug window showed this line:
[EMAIL PROTECTED]
But there isn't a label @uit in the script. I'm not sure if @uit is a mangled ';quit' - when I edited out ';quit'
from the script the debug window didn't change.
Rough edges, can you improve them?
- run to end of script appears to run only to the end of the current label -- this is useful, so keep it, but a
true 'run to end' would be useful as well
Attention: PowerPro's Web site has moved: http://www.ppro.org
SPONSORED LINKS
| Computer monitoring software | Power pro | Computer and internet software |
| Free computer monitoring software |
YAHOO! GROUPS LINKS
- Visit your group "power-pro" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
