Current implementation:
MethodDeclaration>>#handleMissingBehavior
"self error: ('Cannot install method in unexistent behavior {1}' format:
{(behaviorName asString)})"
(MissingClassError
className: behaviorName asString)
signal
Any reason not to make it:
MethodDeclaration>>#handleMissingBehavior
(MissingClassError
className: behaviorName asString)
signal: 'Cannot install method in unexistent behavior',
behaviorName
asString
?
It seems so obvious that I'm sure I must be missing something important!
-----
Cheers,
Sean
--
View this message in context:
http://forum.world.st/On-Missing-Class-Why-not-describe-error-tp4825681.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
