![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Item i = null problem Topic Summary: Error: "null LockRef parameter was passed into argument" Created On: 23-Jul-2008 23:28 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Hi Kris, I have had the same problem, the only way I found around it is to cast the null statement to being an Item. Item i = (Item null) Not sure what this implies about Item, but its worked for me. Paul | |
![]() |
|
Has anyone ever encountered this error?:
"-R-E- DXL: <//Jupiter/DXL programs/minie.inc:1003> null LockRef parameter was passed into argument position 2 Backtrace: <Line:760> " I get it, seemingly randomly, when using code similar to Situation 1. (in the code section below). The problem arises when f is in fact null. It seems that there is something wrong with the 'null' which is used when declaring a line like: Item i = null I've encountered the problem before in situations where I declare an Item, then set it later, such as Situation 2. In that case I've always gotten around the problem by simply declaring i without setting a value. The problem is that right now I'm working with an overloaded function such as Situation 3. In this case I NEED to set i to a null value. I initially thought about putting the call to the original function inside the if statement, and passing in null directly, but the line myFunction(null) calls the function expecting a Folder, which is itself, and I get a stack overflow. I'm thinking this is a Doors/DXL bug, but I wanted to see if others have had problems with it. It only seems to occur on Items, and I've had it happen on multiple computers, so it's not unique to my machine. We've also upgraded sever versions a couple of times. Thanks, -Kris |
|
![]() |
|
![]() |
|
In some more searching of the Forum here, I found the following thread with brief reference to the problem, but that's it:
https://forum.telelogic.com/cu...catid=17&threadid=4852 -Kris Edited: 24-Jul-2008 at 19:33 by Kris Farrin |
|
![]() |
|
![]() |
|
Hi Kris,
I have had the same problem, the only way I found around it is to cast the null statement to being an Item. Item i = (Item null) Not sure what this implies about Item, but its worked for me. Paul |
|
![]() |
|
![]() |
|
Paul,
Wow, I can't believe that I never tried that, but it does indeed work! Yesterday I tried calling the function with a null cast, i.e. myFunction(Item null), but I wasn't surprised to find that Doors didn't like that. I didn't even think to try casting it in the declaration. This definitely seems like a DXL bug, but I'll add this to the list of workarounds for stupid problems ![]() Thanks a bunch! -Kris |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Item i = null problem
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.