![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: DXL Executable Topic Summary: Created On: 24-Sep-2002 19:19 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi all! I have a question about whether it is possible to compile DXL code in such a way that an end user could use the script, but not view or modify it. I tried looking through the DOORS DXL references I have and could find no mention of such a feature. I am currently using DOORS 5.2.
Thanks, Paras. |
|
![]() |
|
![]() |
|
DXL is interpreted not compiled, so there is never a binary executable stored anywhere. The interpreter interprets each line of DXL and executes it.
I notice several of the built in DOORS functions are implemented with encrypted DXL. For example, I could track down the Module >>Edit >>Open Modes menu and notice that "Open Exclusive" is implemented with a single function called "SetExclusive()", but I could not find the DXL code for that function in the library since its in an encrypted file. Like you, I wanted to hide the guts of my DXL, especially the dangerous ones that insure the user is a DBadmin before executing: lets not let users suppress that check. I contacted Telelogic and they said they deliberately protect their proprietary stuff with encryption. They also said the encryption adds a small amount of execution time since it needs to be decrypted before sending it off to the DXL interpreter. They will not reveal their encryption/decryption programs or strategy, nor let me see the encrypted code. I'm too ignorant to figure out a way of encrypting it myself. - Louie |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
DXL Executable
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.