Hi Eliot. 2017-05-09 21:27 GMT+02:00 Eliot Miranda <[email protected]>:
> Hmmm, classNamed: has always answered nil for nonexistent classes. Did > this get changed? Not sure that's right. Why not add checkedClassNamed: > or some such? I created this issue. I am sure that returning nil from methods is always bad design and many books describe it. Also it is not consistent to #at: method: Smalltalk globals at: #AbsentClass. "=> raise error" Smalltalk globals classNamed: #AbsentClass "=> nil"
