| Argument passing - Subroutines and Functions - Mike Pope |
| Caching in on the Frames Array - Mike Pope |
| QTIPS - Fast Dynamic Array Building |
| QTIPS - Using @Upper.Case and @Lower.Case with Foreign Languages |
| @ATTACK - @Lower.Case |
| @ATTACK - @Upper.Case |
| Sorting out Collation Sequences by Mike Pope |
| @ATTACK - @File.Error |
| @ATTACK - @File.Error.Mode |
| QTIPS - Standardising Error Message Display |
| Version 3 Technical Highlights - ValidateName |
RevMedia FKB
| Document | V2I2A13 |
| Title | @ATTACK - @File.Error |
| Keywords | @FILE.ERROR MFS BFS STATUS() |
| Text | A dynamic array WITH three values Used in PASSING information from MFSs/BFSs back to the CALLING program thus releasing the MFS/BFS FROM the responsibility of coping WITH file io errors under all situations <1> Message Number <2> Standard Error Parameters <3> Additional Error Parameters For further information see p49 of the Advanced Revelation 2 0 Quick Reference Guide and assorted Technical Bulletins NB It has frequently been the case in the past that MFSs/BFSs would make calls to MSG to indicate the CURRENT state of activity WITH Release 2 0 this can destroy the integrity of the file io operation as MSG (and other system subroutines) change the contents of @FILE ERROR To ensure complete safety therefore all CALLS to MSG FROM a BFS/MFS should save the contents of @FILE ERROR (and to be on the safe side STATUS()) before the call and restore it AFTER the call Can be amended (Volume 2 Issue 2 Pages 10 11) |
Page last modified: 30/01/03