REVMEDIA FKB Articles - AREV, OI, REV G, jREV, JCDC, LIVEWATER,ADVANCED REVELATION, OPENINSIGHT, REVELATION G

RevMedia FKB

Document	V3I10A9
Title	A RevTechie Replies - And Miscellaneous Jottings - Mike Pope - Revelation Technologies (UK) Ltd
Keywords	READ LOCK SCRIBE OSERROR @VARIABLES @CRTHIGH @PRINTMODE @PDISK.ON MSG MESSAGE ERROR INPUT INPUT.CHAR BREAK-ON
Text	(In fairness to Mike and his wonderful grasp of English I should point out that this is paraphrased FROM a number of his letters unless explicitly quoted AMcA) "David Sigafoos called me up WITH a weird weird problem about locking and reading It seems that the READ STATEMENT is happy enough to get a key WITH value marks in it however bad an idea that might be in real life The LOCK STATEMENT on the other hand is more 'intelligent' and like OCONV treats such a key as a list of keys duly LOCKING each one individually This is an anomaly in what you would otherwise expect to be parallel statements" AMcA Note that if one of the locks in such a LOCK STATEMENT fails no error flag is set and the THEN clause executes Note further that if you keep getting messages about an index node missing regardless of how many times you rebuild your INDEXES the problem might be a value mark in one or more record keys Ever had the experience that when you bring up some OBJECT code in the editor you get the "Changes " message when you want out? Seems that SCRIBE strips trailing delimiters (any system delimiter that is) as a defence against [Enter] happy users At the moment there is no way around this On another point do your readers understand that the symbol table is only used by the debugger? Within a program VARIABLES are referenced by offset within the descriptor table Volume 3 Issue 8 OSERROR This routine is precisely as you note It is a bonding related routine called FROM the OS file BONDS The ARGUMENTS are (properly) LABELLED CODE BFS NAME and STATUS all obviously out of the BFS args @Vars I don't know if you are aware of it but you are providing a fix for the sample code in TB57 which does indeed try to @CRTHIGH = 3 (Hal Wyman explains that this strange behaviour is because "some of the @Variables are SysCom VARIABLES which are compiled normally Others are actually values stored in the engine itself and assignments to them are a special case since there are no descriptors for them Other engine VARIABLES are @Printmode and @Pdisk On They are stored in the engine because they are needed by the print routines within the engine") Interrupt proof error messages "If I don't want users to go anywhere while I've got them captive in a message I use RCI as the type which causes MSG to use the INPUT STATEMENT not INPUT CHAR To suppress DISPLAY you can then do an ECHO OFF " Break On Discussion "All this zero length stuff introduces the problem of an offset AVERAGE and total both of which forget to forget about the inter COLUMN SPACE that isn't when you have a zero length FIELD Ergo offset by one No fix at the moment other than genning code " (Volume 3 Issue 10 PAGE 6)

[revmedia/copyrigh.htm]

Page last modified: 08/02/03