![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Note about "choice" DBE and it's array Topic Summary: don't let a null string get into your array! No DOORS error. Created On: 1-Jun-2007 16:20 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Just a quick "lesson learned" for you coders out there: One of the arguments for the DBE choice() is an array of strings. However, if you don't populate all of the elements of that array before passing it to the choice DBE then get ready for the Diagnostics Log window to pop up as soon as you try to show the DB containing the choice DBE! DOORS does not generate a DXL error that you can trace to a line of code. It just says there's been an access violation and then begins misbehaving! See the attached code for an example.
Jason
|
|
![]() |
|
![]() |
|
The DXL interpreter is very unforgiving if you pass a null or an uninitialised parameter.
You should always ensure that variables are initialised when declared and that you check for null before passing parameters. One exception to this is that I never initialise an Item variable to null as this sometimes causes DXL errors, don't know why, never got to the bottom of it. // this is good Module m = null // this is bad - sometimes causes an error Item i = null ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Note about "choice" DBE and it's array
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.