|
|
|||||||
How can I pause my script line by line? |
||||||||
|
|
|||||||
code:hth"Paused ... hit any key to continue" Jochen [ 04. October 2002, 00:50: Message edited by: jpols ] |
||||||||
|
|
|||||||
Steve, You can also do.. In the script add a line: code:You can also do -DEBUG ON kix32 yourscript /d HTH, Kent |
||||||||
|
|
|||||||
ahh ... missed 'line by line' Sorry ! |
||||||||
|
|
|||||||
Dear, It isn't very clear what his goal is. Possible he want to debug his script. For this situation it can be very frustrating when you need to entry an enormous amount of ENTERs to get to the point. Mostly a big frustation, when you are to late to stop at crucial point. To solve this problem we advise you to use our tool kixstrip, which can add addi- tional to your script. The new makes it possible to see - which lines were executed - what was the last status of execution - what was the moment of execution - etc. On our site you find also kixstrip.pdf documentation. greetings. btw: symbol on our homepage has been linked to related http://kixtart.org topic. |
||||||||
|
|
|||||||
MCA, You are right.. However.. His question was - >> How can I pause my script line by line? I believe we have covered the answer with either /d or debug_on. However... The KiXstrip solution would work too. But, if it is only a few lines, is that really appropriate? He could also add in some @error, @serror handling too.. That way, if an error occurred, it would generate or alert to a problem. Additionally, I will find myself running a large script with an issue from the command line, so the results don't just pass by. Just some thoughts. Kent |
||||||||
|
|
|||||||
...of course, one could always go to sleep... |
||||||||
|
|
|||||||
kent, I think scanning technology is the best: split into half. the erroring side, split to half... and so on until on single line. not so quick maybe but you don't need to do so much. |
||||||||
|
|
|||||||
Jooel, You are taking me back the days of Calculus! I was thinking along those lines too.. That is, if you have a section of script that is in question, break it out to test file run it.. Then debug and when complete, put it back in. Kent |