Pro-IV Variables
Started by davethehun, Sep 20 2004 10:08 AM
8 replies to this topic
#1
Posted 20 September 2004 - 10:08 AM
Hello everybody,
The documentation lists a number of these variables e.g @OPR, @DATE and so on, but there appears to be loads of others that I have read about on these pages and can't find any documentation for e.g. @CURLSNAME. Is there a complete list of these variables somewhere?
Thanks
David
The documentation lists a number of these variables e.g @OPR, @DATE and so on, but there appears to be loads of others that I have read about on these pages and can't find any documentation for e.g. @CURLSNAME. Is there a complete list of these variables somewhere?
Thanks
David
#3
Posted 20 September 2004 - 01:00 PM
Unfortunately our guest is correct. They are not listed in any one place in the documentation. When a new version comes out, we do a string search of the kernel which is the pro.exe (windows) and pro (Unix) executable. In Unix you can use the following command: strings pro | grep @ > textfile
It would be nice if the docs were more thorough.
Lew
It would be nice if the docs were more thorough.
Lew
#7
Posted 21 September 2004 - 09:19 AM
If we just post them all in here (ie on this thread) to start with, I'll tidy it up and create a single list.
Then I'll post it as a single topic and make it 'Sticky' so it stays at the top, like the 'Documentation' post...
Rob.
Then I'll post it as a single topic and make it 'Sticky' so it stays at the top, like the 'Documentation' post...
Rob.
#9
Posted 22 September 2004 - 04:15 PM
Note:
Some of these are not variables - @LITERAL is the key used for storing changes to the default strings (see other threads)
@RFUNCT appears twice - once is a reference to the variable and once to the actual Function (I think). @SFUNCT is also a reference to the Function name to be called if no Security Link function is present.
Anyone want to cross-reference this against the manual & see what's not documented there?
Some of these are not variables - @LITERAL is the key used for storing changes to the default strings (see other threads)
@RFUNCT appears twice - once is a reference to the variable and once to the actual Function (I think). @SFUNCT is also a reference to the Function name to be called if no Security Link function is present.
Anyone want to cross-reference this against the manual & see what's not documented there?
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users