Class: AmbiguousMessage

• Inheritance
• Description
• Class protocol
  • testing

Inheritance:

   Object
   |
   +--GenericException
      |
      +--Exception
         |
         +--Error
            |
            +--ProceedableError
               |
               +--ExecutionError
                  |
                  +--AmbiguousMessage

Package:

stx:libbasic

Category:

Kernel-Exceptions-ExecutionErrors

Version:

rev: 1.5 date: 2016/09/27 10:51:14

user: cg

file: AmbiguousMessage.st directory: libbasic

module: stx stc-classLibrary: libbasic

Description:

raised by the VM when a message is sent to an object and 
is not clear which method to execute.
Such situation may occur when a current selector namespace
imports two namespaces and both define a method with the
requested selector.

copyright
COPYRIGHT (c) 2010 by Jan Vrany, SWING Research Group. CTU in Prague
             All Rights Reserved

Permission is hereby granted, free of charge, to any person
obtaining a copy of this software and associated documentation
files (the 'Software'), to deal in the Software without
restriction, including without limitation the rights to use,
copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the
Software is furnished to do so, subject to the following
conditions:

The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.

Class protocol:

 isProgramError

redefined in all exceptions which are programmer's errors,
and which should probably not be ignored.
I.e. a global error handler should reject and let a debugger get control.