![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: DXL Debugger Topic Summary: Created On: 23-Jun-2006 17:01 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: No, there is no debugger for DXL. I rely on print statements for debugging. A simple technique I use is to declare a global variable called DEBUG and a function called debugPrint(string) to do your printing instead of calling print directly. You can then turn debugging on/off by setting the variable. e.g, bool DEBUG = true void debugPrint(string msg) { if (DEBUG) { print msg "\n" } } If you have a non-trivial data structure, especially using arrays and skips, then I recommend that you write a function that prints the data structure. Very useful. You could also take a look at the function checkDXL() which allows you to perform a static check of DXL before you actually run it. | |
![]() |
|
Does DXL have a debugger?
|
|
![]() |
|
![]() |
|
No, there is no debugger for DXL.
I rely on print statements for debugging. A simple technique I use is to declare a global variable called DEBUG and a function called debugPrint(string) to do your printing instead of calling print directly. You can then turn debugging on/off by setting the variable. e.g, bool DEBUG = true void debugPrint(string msg) { if (DEBUG) { print msg "\n" } } If you have a non-trivial data structure, especially using arrays and skips, then I recommend that you write a function that prints the data structure. Very useful. You could also take a look at the function checkDXL() which allows you to perform a static check of DXL before you actually run it. ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
Mostly I rely on print statements as Tony mentions or writing info to a logfile.
There are some DXL trace statements as well though. print dxlHere() "\n" prints line number and which DXL file you are in - useful when using lots of includes. startDXLTracing_("C:\\Your Dir\\Your File.txt") stopDXLTracing_ Logs DXL actions to the file listed can be useful but uses a very verbose language so the file gets big fast! also slows execution down. ------------------------- Graham Stradling, Alcatel-Lucent. |
|
![]() |
|
![]() |
|
Thanks guys. I guess I was just amazed by how such large and complicated scripts can be built without a debugger - so I guess the answer is very carefully
![]() |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
DXL Debugger
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.