![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: DXL script that worked in 7.1 no longer works in 8.1 Topic Summary: Created On: 10-Jan-2007 19:39 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: It was the "o=target l" command. Once I changed it to "Object o = target l" (and changed "string m" to be "string mName" for clarity) it worked. This was part of an include file from some legacy routines. Some of our other script libraries are intermittantly working oddly too. I suspect that they also have some includes from legacy scripts. Thanks for the help! | |
![]() |
|
Has anyone heard or seen any differences in the handling of DXL between DOORS 7.1 and 8.1? It seems to not like function calls that don't explicitly have the "()"s and also didn't like o."Object Text" to reference object text, at least in this one function....
I had an included file of functions that included one one attached. It worked fine in 7.1 but gets the following errors in 8.1: Error message was ![]() Here is what I get: -E- DXL: <R/Reports/csv_Write_routines.inc:180> incorrect arguments for function (number) Included from: <Line:164> -E- DXL: <R/Reports/csv_Write_routines.inc:184> incorrect arguments for (.) Included from: <Line:164> -E- DXL: <R/Reports/csv_Write_routines.inc:185> incorrect arguments for (.) Included from: <Line:164> -E- DXL: <R/Reports/csv_Write_routines.inc:185> incorrect arguments for (=) Included from: <Line:164> -E- DXL: <R/Reports/csv_Write_routines.inc:184> incorrect arguments for (if) Included from: <Line:164> -E- DXL: <R/Reports/csv_Write_routines.inc:184> incorrect arguments for function (canRead) Included from: <Line:164> -E- DXL: <R/Reports/csv_Write_routines.inc:188> incorrect arguments for function (number) Included from: <Line:164> -I- DXL: all done with 7 errors and 0 warnings |
|
![]() |
|
![]() |
|
You are getting DXL interpret errors which means it has not yet looked at your module.
I see that you fail to define variable 'o' as type 'Object', and let it get defined explicitely. You should always define the variables but that's another story. You define 'o' with the "o = target l" command. I suspect that in v7.1 that turned out to be type Object, but in v8.1 its some other type; perhaps v8.1 DXL added a new 'target' command. Add this line to your startup.dxl file: XFLAGS_ &=~AutoDeclare_ // Disallow auto-declare of variables; insist all are explicitely defined That will turn off auto-declare and your undeclared variables will be identified explicitly. - Louie |
|
![]() |
|
![]() |
|
It was the "o=target l" command. Once I changed it to "Object o = target l" (and changed "string m" to be "string mName" for clarity) it worked. This was part of an include file from some legacy routines.
Some of our other script libraries are intermittantly working oddly too. I suspect that they also have some includes from legacy scripts. Thanks for the help! |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.