Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
Topic Title: Getting a LinkRef from a Link
Topic Summary:
Created On: 8-Mar-2005 20:11
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
Answer This question was answered by Kirk Walker, on Friday, March 11, 2005 4:49 PM

Answer:
 8-Mar-2005 20:11
User is offline View Users Profile Print this message


Kirk Walker

Posts: 32
Joined: 18-Sep-2004

I am trying to fix some dxl that used to work when all of the database was a flat structure, but now that some specs are in one folder and other specs in the same project are in other folders, and they all are at varying levels away from the project's root level, it does not work. Specifically with the following situation:
Link l
LinkRef lref

for l in o<-"*" do {
// stuff
}
but for some of the operations, like getting the module path (fullName) it does not work unless I have the LinkRef instead of the Link.
It would be nice to be able to do somy type of a lref = l

Here is a synopsis of the issues:

(1) Basically I have two loops, one is:
for modname in o<-"*" do { // open sources of incoming links
ModName_ srcModNm = module(modname)
// srcModNm is always null, because it doesn't have a fullname and the module is in a
// different branch of the folder structure (up one, other branch, and down a few levels)
// I cannot figure out where to legally stick a fullName or a read that will get me the long path name or srcModNm...

and the other issue is

(2) for l in o<-"*" do { // count incoming links
modname = fullName(module l) // incoming link module name
// but the above line is null and gets nothing, even if there IS an inlink,
// because the link source is in a different branch of the tree

Now if I instead do the following:\
for lref in o<-"*" do {
modname = fullName(module lref) // incoming link module name
// this works, modname is not null, but some of my later operations
// in the loop must have an "l", not an "lref" to work (source statements, etc)


I should probably note that because of the way the operations perform some of their steps, I cannot separate out the 2nd loop into two loops (an "l" loop and an "lref" loop). What I need to figure out is how to get an "lref" from an "l" or vice versa.

Any suggestions?


Edited: 9-Mar-2005 at 13:14 by Kirk Walker
Report this to a Moderator Report this to a Moderator
 8-Mar-2005 21:46
User is offline View Users Profile Print this message


Kirk Walker

Posts: 32
Joined: 18-Sep-2004

Answer Answer


Edited: 9-Mar-2005 at 13:15 by Kirk Walker
Report this to a Moderator Report this to a Moderator
 6-Jul-2005 01:06
User is offline View Users Profile Print this message


James Steuwe

Posts: 1
Joined: 30-Jun-2005

Just starting to look at DXL examples and running across similiar problems. In my case I need to chase out-links and when I reach a certain document, chase the in-links for 2 levels searching for specific document and text.

Testing of some others code ran across similiar issues so I would be interested in hearing of any successes.

James.Steuwe@maf.nasa.gov
James_Steuwe@hotmail.com
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 0 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 0 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.