|
Gregory McLeod
Registered User
Join date: 21 Oct 2006
Posts: 278
|
06-20-2007 08:11
Is there a facility to step through a script line by line examining variables etc?
|
|
AnnMarie Otoole
Addicted scripter
Join date: 6 Jan 2007
Posts: 162
|
06-20-2007 12:35
No. At places where you wan't to investigate the results of an instruction you insert a temporary line:-
llOwnerSay("Variable XYZ = "+(string)XYZ);
That will print out the vaue at that stage of the processing.
|
|
Newgate Ludd
Out of Chesse Error
Join date: 8 Apr 2005
Posts: 2,103
|
06-20-2007 12:42
From: Gregory McLeod Is there a facility to step through a script line by line examining variables etc? Only by hand cranking it. You could look at the stand alone LSL Compiler that is mentioned in the forums someplace, I was unfortunately unable to find it myself to paste you a link.
_____________________
I'm back......
|
|
Gregory McLeod
Registered User
Join date: 21 Oct 2006
Posts: 278
|
06-21-2007 00:27
From: AnnMarie Otoole No. At places where you wan't to investigate the results of an instruction you insert a temporary line:-
llOwnerSay("Variable XYZ = "+(string)XYZ);
That will print out the vaue at that stage of the processing. That is what I am doing but it causes problems with memory usage unless you add and remove (with commenting //) between tests. It becomes tedious and slows down the development process. Thanks for the thought and reply. |
|
Gregory McLeod
Registered User
Join date: 21 Oct 2006
Posts: 278
|
06-21-2007 00:28
From: Newgate Ludd Only by hand cranking it.
You could look at the stand alone LSL Compiler that is mentioned in the forums someplace, I was unfortunately unable to find it myself to paste you a link. I think I will have to investigate it and find out what it can do. Thanks. |
|
MarquisDe Paine
Registered User
Join date: 20 Jun 2007
Posts: 34
|
06-21-2007 02:13
How about building a generic debugging function, whose output is controlled by a single global constant. You'd use the function to enable/disable outputting of debug info instead of constantly commenting/uncommenting stuff.
Should be removed prior to finalization, but maybe slightly less tedious than the "by hand"-approach?
|
|
Gregory McLeod
Registered User
Join date: 21 Oct 2006
Posts: 278
|
06-21-2007 06:52
From: Newgate Ludd Only by hand cranking it.
You could look at the stand alone LSL Compiler that is mentioned in the forums someplace, I was unfortunately unable to find it myself to paste you a link. Did you mean the LSL Editor from Alphons van der Heijden? If so I cannot find any reference to stepping through the code statement by statement. |
|
Gregory McLeod
Registered User
Join date: 21 Oct 2006
Posts: 278
|
06-21-2007 06:56
From: MarquisDe Paine How about building a generic debugging function, whose output is controlled by a single global constant. You'd use the function to enable/disable outputting of debug info instead of constantly commenting/uncommenting stuff.
Should be removed prior to finalization, but maybe slightly less tedious than the "by hand"-approach? A very good idea but what I am really looking for is something like an IDE such as you find with VB and other such development tools. The execution of my scripts is very tortuous because of the other LSL limitations. I have scripts in 10 of the linked prims and in the rezzed pieces (up to 80). Thanks for the thought. |