Hi Denis, On Tue, May 9, 2017 at 2:47 PM, Denis Kudriashov <[email protected]> wrote:
> > 2017-05-09 22:16 GMT+02:00 Eliot Miranda <[email protected]>: > >> I get that. But there's lots of code out there that expects classNamed: >> to answer nil for names tat don't name a class. Why break all that code? >> If you had added checkedClassNamed: or some thing else then that old code >> wouldn't be broken. There needs to be some cheap way of checking whether a >> class with a specific name actually exists. classNamed: fulfilled that >> need. By redefining it you'e meant that that has to be reimplemented. >> It's not a good idea to redefine co=re behavior in this way. It breaks >> lots of code (including VMMaker). > > > You know Pharo is going own way. We want improve bad things. That's why > #name will be removed from Object in next Pharo version. That's why Pragma > #selector is deprecated. It is hard to do but we want move. > In case of #classNamed: users should be fixed. Maybe other people have > different opinion? > OK. Sio w -- _,,,^..^,,,_ best, Eliot
