| Argument passing - Subroutines and Functions - Mike Pope |
| Caching in on the Frames Array - Mike Pope |
| QTIPS - Fast Dynamic Array Building |
| RTP Series - RTP50 |
| @ATTACK - @Messages |
| Advanced Revelation Initialisation Sequence (Overview) by Mike Pope |
| Caching in on the Frames Array - Mike Pope |
| QTIPS - Using @Upper.Case and @Lower.Case with Foreign Languages |
| @ATTACK - @Lower.Case |
| @ATTACK - @Upper.Case |
| Sorting out Collation Sequences by Mike Pope |
| SecureUser |
| VERBatim - V25 |
| @ATTACK - @Files.System |
| Advanced Revelation Initialisation Sequence (Overview) by Mike Pope |
| REVMEDIA Revisted |
RevMedia FKB
| Document | V2I4A10 |
| Title | @ATTACK - @Messages |
| Keywords | @MESSAGES IN.MEMORY MSG |
| Text | An @RM delimited array of messages kept in memory Used for frequently called messages to prevent the overhead of disk access before display The format of the array is as follows @RM <1> Message Key <2 n> Message Record @RM Messages may be automatically buffered in @MESSAGES AFTER they have been called by SETTING the Message Type to "B" The documentation indicates that setting the Message Type to "R" results in the message being read at logon and subsequently buffered This is not the case To achieve this functionality the message id must be added into a record called IN MEMORY in the Messages file Can be amended Note that when MSG is called WITH a literal the system does not realise this It tries to read the messages file to see if a record exists WITH a key equal to the literal This can slow down message display especially on networks There is a feature in Release 2 0 that indicates the messages file is not to be checked To take advantage of this set MAP<13> to 1 (See README file Release Diskettes) (Volume 2 Issue 4 Pages 9 10) |
Page last modified: 30/01/03