--- a/Signal.st Wed Jul 06 16:39:05 2016 +0200
+++ b/Signal.st Wed Jul 06 16:43:04 2016 +0200
@@ -1,5 +1,3 @@
-"{ Encoding: utf8 }"
-
"
COPYRIGHT (c) 1993 by Claus Gittinger
All Rights Reserved
@@ -41,20 +39,20 @@
documentation
"
Note:
- The instance based Signal framework is being replaced by class based exceptions.
- I.e. what used to be instances of Signal/QuerySignal is beeing
- rewritten into subclasses of Exception/Error/Query and Warning.
+ The instance based Signal framework is being replaced by class based exceptions.
+ I.e. what used to be instances of Signal/QuerySignal is beeing
+ rewritten into subclasses of Exception/Error/Query and Warning.
- Although the functionality is basically unchanged, the new
- class based exceptions are easier to instanciate (no need for
- creation in a classes initialize method), easier to use (no real
- need for Signal-constant accessors) and allow for easier parameter
- passing (not only a single parameter, but allows for individual
- exception subclasses to add additional state).
+ Although the functionality is basically unchanged, the new
+ class based exceptions are easier to instantiate (no need for
+ creation in a classes initialize method), easier to use (no real
+ need for Signal-constant accessors) and allow for easier parameter
+ passing (not only a single parameter, but allows for individual
+ exception subclasses to add additional state).
- However, the old Signal hierarchy will remain in existance, since it allows
- funny instance-specific and anonymous exception handling schemes to be
- implemented, which are hard to built using class-based exceptions.
+ However, the old Signal hierarchy will remain in existance, since it allows
+ funny instance-specific and anonymous exception handling schemes to be
+ implemented, which are hard to built using class-based exceptions.
Signal and Exception provide a framework for exception handling.
@@ -107,34 +105,34 @@
[Instance variables:]
- mayProceed <Boolean> hint for the debugger - program may
- proceed (currently not honored by the
- debugger)
+ mayProceed <Boolean> hint for the debugger - program may
+ proceed (currently not honored by the
+ debugger)
- notifierString <String> error message to be output
+ notifierString <String> error message to be output
- nameClass <Class> for the printOn-implementation; nameClass
- is the class, to which message (below)
- should be sent to create the receiver.
+ nameClass <Class> for the printOn-implementation; nameClass
+ is the class, to which message (below)
+ should be sent to create the receiver.
- message <Symbol> for the printOn-implementation; message
- is the selector, which should be sent to
- nameClass (above) to create the receiver.
+ message <Symbol> for the printOn-implementation; message
+ is the selector, which should be sent to
+ nameClass (above) to create the receiver.
- handlerBlock <Block> if nonNil, a 1-arg block to be
- evaluated when no handler context is
- found. The block gets the exception
- object as argument. This will play the role
- of an on-stack handler.
+ handlerBlock <Block> if nonNil, a 1-arg block to be
+ evaluated when no handler context is
+ found. The block gets the exception
+ object as argument. This will play the role
+ of an on-stack handler.
[author:]
- Claus Gittinger
+ Claus Gittinger
[see also:]
- GenericException
- SignalSet QuerySignal
- Object
- (``Exception handling and signals'': programming/exceptions.html)
+ GenericException
+ SignalSet QuerySignal
+ Object
+ (``Exception handling and signals'': programming/exceptions.html)
"
! !