![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Baseline Loop Topic Summary: Created On: 2-Nov-2007 14:45 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Attached is a standard strategy for dealing with the baselines of a module.
Ran into a wierd exception violation associated with running through the baselines of an open module. I had previously run into this when the main program had a baseline loop and called a library function that likewise looped through the baselines of the same module; DOORS didn't like that. The solution was to first stage the baselines in a skip and then deal with them then. I could not figure out what was wrong in this new situation, but I now conclude that you should ALWAYS stage the baselines of a module in a Skip list before dealing with them. See attached for example. This technique is needed in some other situations and should be in the back of the programmer's mind; such as dealing with the links of an object. One such mandatory situation is when you are going to be deleting the loop variable (e.g. deleting one of the outlinks of an object) and you don't want to be in the middle of a do-loop when deleting: for lnk in obj ->"*" {delete(lnk)} can cause problems. The key feature of the attached is retrieving them from the Skip list in the exact order they were found. The 'Sequencer' variable as the Key of the skip list accomplishes that. - Louie |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Baseline Loop
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.