Difference: PUSHPOPILFStatements (7 vs. 8)

Revision 82008-05-14 - PeteBrower

Line: 1 to 1
 
META TOPICPARENT name="APPX43Features"

New ILF Statements

Line: 73 to 73
 Also related to this new statement is a new Pre-Defined Field called --- ACCESS PATH. As one might assume, the field contains the value of the current access path for the Process Control File. The field may be viewed, but not changed via ILF code (that is to say, an ILF statement to SET --- ACCESS PATH to a specified value will be ignored).

Open Issues, Bugs, Suggestions

Added:
>
>
OPEN -
 Note that PUSHing a field after PUSHing a record containing that field will not cause the field value on the PUSHed record to change. The stack for the RECORD is independent from that of the field. This is a different behavior than designers may be used to from the STORE/RESTORE statements.
Changed:
<
<
It appears that fields with multiple occurrences ARE NOT
>
>
OPEN - It appears that fields with multiple occurrences ARE NOT
 supported by multiple stacks. For example, PUSH value 1 into field occurrence 1, then PUSH value 2 into field occurrence 2. If you then execute a POP on the field occurrence 1, it will retrieve the last
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback