--- a/Exception.st Thu May 09 15:24:26 1996 +0200
+++ b/Exception.st Thu May 09 15:24:48 1996 +0200
@@ -90,7 +90,6 @@
[Class variables:]
-
EmergencyHandler <Block> this block is evaluated, if no handler was defined
for a signal (i.e. this one is responsible for the
unhandled exception debugger).
@@ -105,9 +104,10 @@
[see also:]
- Signal SignalSet
+ Signal SignalSet QuerySignal
Context Block
Object DebugView
+ (``Exception handling and signals'': programming/exceptions.html)
[author:]
Claus Gittinger
@@ -363,6 +363,7 @@
con := thisContext sender. "the raise-context"
con := con sender. "the signal raise context"
con isRecursive ifTrue:[
+ con := nil.
"
mhmh - an error while in a handler
"
@@ -477,7 +478,7 @@
"... and call it"
^ block value:self.
- "Modified: 23.3.1996 / 17:16:13 / cg"
+ "Modified: 9.5.1996 / 15:04:30 / cg"
!
raise
@@ -511,6 +512,6 @@
!Exception class methodsFor:'documentation'!
version
- ^ '$Header: /cvs/stx/stx/libbasic/Exception.st,v 1.35 1996-04-25 16:47:14 cg Exp $'
+ ^ '$Header: /cvs/stx/stx/libbasic/Exception.st,v 1.36 1996-05-09 13:24:48 cg Exp $'
! !
Exception initialize!
--- a/QuerySig.st Thu May 09 15:24:26 1996 +0200
+++ b/QuerySig.st Thu May 09 15:24:48 1996 +0200
@@ -41,9 +41,13 @@
signal. Thus, these bypass anySignal handlers.
If unhandled, no error is raised, instead they are simply ignored
(as opposed to normal signals, which raise an unhandled signal exception).
+ QuerySignals are also ignored, if a handler exists, but rejects.
- Their main use is to implement up-Queries via signals even if intermediate
- errorSignal handlers are present (which is not possible with ordinary signals).
+ Their main use is to implement up-Queries via signals, that work even
+ if intermediate errorSignal handlers are present
+ (which is not possible with ordinary signals, since errorSignal handlers
+ would catch those signals).
+
Code deep down in the calling hierarchy can post such an up-Query to ask
for some information in return or to pass some information upward.
@@ -58,6 +62,7 @@
[see also:]
Signal SignalSet Exception
Object
+ (``Exception handling and signals'': programming/exceptions.html)
[author:]
Claus Gittinger
@@ -126,5 +131,5 @@
!QuerySignal class methodsFor:'documentation'!
version
- ^ '$Header: /cvs/stx/stx/libbasic/Attic/QuerySig.st,v 1.10 1996-04-27 18:00:44 cg Exp $'
+ ^ '$Header: /cvs/stx/stx/libbasic/Attic/QuerySig.st,v 1.11 1996-05-09 13:23:57 cg Exp $'
! !
--- a/QuerySignal.st Thu May 09 15:24:26 1996 +0200
+++ b/QuerySignal.st Thu May 09 15:24:48 1996 +0200
@@ -41,9 +41,13 @@
signal. Thus, these bypass anySignal handlers.
If unhandled, no error is raised, instead they are simply ignored
(as opposed to normal signals, which raise an unhandled signal exception).
+ QuerySignals are also ignored, if a handler exists, but rejects.
- Their main use is to implement up-Queries via signals even if intermediate
- errorSignal handlers are present (which is not possible with ordinary signals).
+ Their main use is to implement up-Queries via signals, that work even
+ if intermediate errorSignal handlers are present
+ (which is not possible with ordinary signals, since errorSignal handlers
+ would catch those signals).
+
Code deep down in the calling hierarchy can post such an up-Query to ask
for some information in return or to pass some information upward.
@@ -58,6 +62,7 @@
[see also:]
Signal SignalSet Exception
Object
+ (``Exception handling and signals'': programming/exceptions.html)
[author:]
Claus Gittinger
@@ -126,5 +131,5 @@
!QuerySignal class methodsFor:'documentation'!
version
- ^ '$Header: /cvs/stx/stx/libbasic/QuerySignal.st,v 1.10 1996-04-27 18:00:44 cg Exp $'
+ ^ '$Header: /cvs/stx/stx/libbasic/QuerySignal.st,v 1.11 1996-05-09 13:23:57 cg Exp $'
! !