User Tools

Site Tools


cascaded_20on_20close_20handling

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
cascaded_20on_20close_20handling [2018/04/14 20:39] – Added syntax highlighting richardrussellcascaded_20on_20close_20handling [2024/01/05 00:22] (current) – external edit 127.0.0.1
Line 41: Line 41:
  
         DEF PROCclose         DEF PROCclose
-        IF !392 PROC(^@%+392) ELSE QUIT+        LOCAL c%% 
 +        c%% = PAGE - !340 + !392 
 +        IF !392 PROC(^c%%) ELSE QUIT
         ENDPROC         ENDPROC
 </code> </code>
  
 Note that in a real-world example the final ON CLOSE handler would probably **QUIT** the program. That isn't done here because the displayed output would disappear!\\ \\  There is a theoretical possibility that an ON CLOSE event could occur //between// the **ON CLOSE** and **ON ERROR** statements in PROC0. In that very unlikely circumstance, the close would be handled as an error. Apart from the user receiving an unexpected message, it should be harmless. Note that in a real-world example the final ON CLOSE handler would probably **QUIT** the program. That isn't done here because the displayed output would disappear!\\ \\  There is a theoretical possibility that an ON CLOSE event could occur //between// the **ON CLOSE** and **ON ERROR** statements in PROC0. In that very unlikely circumstance, the close would be handled as an error. Apart from the user receiving an unexpected message, it should be harmless.
cascaded_20on_20close_20handling.1523738355.txt.gz · Last modified: 2024/01/05 00:18 (external edit)