Monitor current line number while running DWScript?
up vote
0
down vote
favorite
I'm using the latest DWScript which has a TdwsDebugger component with it. However I'm not necessarily looking to provide debugging tools to the user - just visually show the current line number.
In the TdwsDebugger component, in its OnDebug event, expr.ScriptPos seems to provide me with this information. But I'm trying to figure out how to make use of this without actually "debugging".
How can I show current DWScript line number without implementing debugging?
delphi dwscript
asked Nov 11 at 16:42
Jerry Dodge
15.1k21107260
add a comment |
up vote
0
down vote
favorite
I'm using the latest DWScript which has a TdwsDebugger component with it. However I'm not necessarily looking to provide debugging tools to the user - just visually show the current line number.
In the TdwsDebugger component, in its OnDebug event, expr.ScriptPos seems to provide me with this information. But I'm trying to figure out how to make use of this without actually "debugging".
How can I show current DWScript line number without implementing debugging?
delphi dwscript
asked Nov 11 at 16:42
Jerry Dodge
15.1k21107260
A SynEdit memo could display the script and highlight the executing line.
– MartynA
Nov 11 at 16:49
@MartynA Indeed, I'm usingTSynEdit, but I need access to the current line # from DWS.
– Jerry Dodge
Nov 11 at 16:58
2
I took a quick look at the DWScript source at it's not glaringly obvious how to do this, but equally, it's not clear how you could do what you want without actually debugging: after all, if DWS has a free-running execution engine, it wouldn't (and shouldn't, itself) have any concept of a current line. So I'm guessing that this info is only available when it's being driven by a debugger, whose business it is to know how to keep track of the source code statement which corresponds to the currently-executing code. Iyswim ...
– MartynA
Nov 11 at 18:43
Generally, it's the act of debugging that allows a program to inspect execution state of another program. So I think you do need to be debugging to know that.
– David Heffernan
Nov 12 at 7:26
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm using the latest DWScript which has a TdwsDebugger component with it. However I'm not necessarily looking to provide debugging tools to the user - just visually show the current line number.
In the TdwsDebugger component, in its OnDebug event, expr.ScriptPos seems to provide me with this information. But I'm trying to figure out how to make use of this without actually "debugging".
How can I show current DWScript line number without implementing debugging?
delphi dwscript
asked Nov 11 at 16:42
Jerry Dodge
15.1k21107260
I'm using the latest DWScript which has a TdwsDebugger component with it. However I'm not necessarily looking to provide debugging tools to the user - just visually show the current line number.
In the TdwsDebugger component, in its OnDebug event, expr.ScriptPos seems to provide me with this information. But I'm trying to figure out how to make use of this without actually "debugging".
How can I show current DWScript line number without implementing debugging?
delphi dwscript
delphi dwscript
asked Nov 11 at 16:42
Jerry Dodge
15.1k21107260
asked Nov 11 at 16:42
Jerry Dodge
15.1k21107260
asked Nov 11 at 16:42
Jerry Dodge
15.1k21107260
asked Nov 11 at 16:42
Jerry Dodge
15.1k21107260
asked Nov 11 at 16:42
Jerry Dodge
15.1k21107260
15.1k21107260
A SynEdit memo could display the script and highlight the executing line.
– MartynA
Nov 11 at 16:49
@MartynA Indeed, I'm usingTSynEdit, but I need access to the current line # from DWS.
– Jerry Dodge
Nov 11 at 16:58
2
I took a quick look at the DWScript source at it's not glaringly obvious how to do this, but equally, it's not clear how you could do what you want without actually debugging: after all, if DWS has a free-running execution engine, it wouldn't (and shouldn't, itself) have any concept of a current line. So I'm guessing that this info is only available when it's being driven by a debugger, whose business it is to know how to keep track of the source code statement which corresponds to the currently-executing code. Iyswim ...
– MartynA
Nov 11 at 18:43
Generally, it's the act of debugging that allows a program to inspect execution state of another program. So I think you do need to be debugging to know that.
– David Heffernan
Nov 12 at 7:26
add a comment |
A SynEdit memo could display the script and highlight the executing line.
– MartynA
Nov 11 at 16:49
@MartynA Indeed, I'm usingTSynEdit, but I need access to the current line # from DWS.
– Jerry Dodge
Nov 11 at 16:58
2
I took a quick look at the DWScript source at it's not glaringly obvious how to do this, but equally, it's not clear how you could do what you want without actually debugging: after all, if DWS has a free-running execution engine, it wouldn't (and shouldn't, itself) have any concept of a current line. So I'm guessing that this info is only available when it's being driven by a debugger, whose business it is to know how to keep track of the source code statement which corresponds to the currently-executing code. Iyswim ...
– MartynA
Nov 11 at 18:43
Generally, it's the act of debugging that allows a program to inspect execution state of another program. So I think you do need to be debugging to know that.
– David Heffernan
Nov 12 at 7:26
A SynEdit memo could display the script and highlight the executing line.
– MartynA
Nov 11 at 16:49
A SynEdit memo could display the script and highlight the executing line.
– MartynA
Nov 11 at 16:49
@MartynA Indeed, I'm using
TSynEdit, but I need access to the current line # from DWS.– Jerry Dodge
Nov 11 at 16:58
@MartynA Indeed, I'm using
TSynEdit, but I need access to the current line # from DWS.– Jerry Dodge
Nov 11 at 16:58
2
2
I took a quick look at the DWScript source at it's not glaringly obvious how to do this, but equally, it's not clear how you could do what you want without actually debugging: after all, if DWS has a free-running execution engine, it wouldn't (and shouldn't, itself) have any concept of a current line. So I'm guessing that this info is only available when it's being driven by a debugger, whose business it is to know how to keep track of the source code statement which corresponds to the currently-executing code. Iyswim ...
– MartynA
Nov 11 at 18:43
I took a quick look at the DWScript source at it's not glaringly obvious how to do this, but equally, it's not clear how you could do what you want without actually debugging: after all, if DWS has a free-running execution engine, it wouldn't (and shouldn't, itself) have any concept of a current line. So I'm guessing that this info is only available when it's being driven by a debugger, whose business it is to know how to keep track of the source code statement which corresponds to the currently-executing code. Iyswim ...
– MartynA
Nov 11 at 18:43
Generally, it's the act of debugging that allows a program to inspect execution state of another program. So I think you do need to be debugging to know that.
– David Heffernan
Nov 12 at 7:26
Generally, it's the act of debugging that allows a program to inspect execution state of another program. So I think you do need to be debugging to know that.
– David Heffernan
Nov 12 at 7:26
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53250907%2fmonitor-current-line-number-while-running-dwscript%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
A SynEdit memo could display the script and highlight the executing line.
– MartynA
Nov 11 at 16:49
@MartynA Indeed, I'm using
TSynEdit, but I need access to the current line # from DWS.– Jerry Dodge
Nov 11 at 16:58
2
I took a quick look at the DWScript source at it's not glaringly obvious how to do this, but equally, it's not clear how you could do what you want without actually debugging: after all, if DWS has a free-running execution engine, it wouldn't (and shouldn't, itself) have any concept of a current line. So I'm guessing that this info is only available when it's being driven by a debugger, whose business it is to know how to keep track of the source code statement which corresponds to the currently-executing code. Iyswim ...
– MartynA
Nov 11 at 18:43
Generally, it's the act of debugging that allows a program to inspect execution state of another program. So I think you do need to be debugging to know that.
– David Heffernan
Nov 12 at 7:26