![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: null module parameter error Topic Summary: null module parameter error Created On: 18-Aug-2005 08:08 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hello all,
Im Trying to run loop that run through all project in database, than all modules in project, and for each of those, i run again a loop for all projects in database, and all modules in project. in the last loop, i get null modules for modules that are completely fine. for instance the function isDeleted on those modules returns true, even though those are fine modules, with complete access rights, and of course not deleted. Ideas? Thanks. Asaf Kivity - ManageWare |
|
![]() |
|
![]() |
|
There are some loop types that cannot be nested. For example you cannot have a "for link in ThisObject" loop within an identical outer loop (for that same object). The inner loop screws up the positioning of the outer loop. The for module in project do loop may well be one of those such loops.
Its better if your main programs routinely find everything they want to work with and put them in some kind of list, then cycle through the list doing the work. I like Skip lists. For example: Skip skpModsInProject = createString() for modules in the project { NameMod = get the module full name put (skpModsInProjet, NameMod, NameMod) } for NameMod in skpModsInProject do { Deal with this module } delete(skpModsInProject). If your inner loop adds or deletes modules then you are in some trouble no matter what you do. I'd add some sort of "is this still a module" check before the "Deal with this module" code. - Louie Also: the Modules in the project loop only finds OPEN modules. To find all modules you need the "for item in project" loop, then check the type(item) to insure its "Formal", and the item is not isDeleted(item). |
|
![]() |
|
![]() |
|
I think you are correct. i used skip lists now, and it seem to work better.
I still think that it is something which is a problem with DXL, luckily, can be workaround. Thanks. |
|
![]() |
|
![]() |
|
Telelogic gets to decides the difference between an "undesirable feature" and a "bug".
|
|
![]() |
Telelogic DOORS
» DXL Exchange
»
null module parameter error
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.