Magritte description comes to mind... --- Philippe Back Dramatic Performance Improvements Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail:[email protected] | Web: http://philippeback.eu Blog: http://philippeback.be | Twitter: @philippeback Youtube: http://www.youtube.com/user/philippeback/videos
High Octane SPRL rue cour Boisacq 101 | 1301 Bierges | Belgium Pharo Consortium Member - http://consortium.pharo.org/ Featured on the Software Process and Measurement Cast - http://spamcast.libsyn.com Sparx Systems Enterprise Architect and Ability Engineering EADocX Value Added Reseller On Tue, Jan 21, 2014 at 6:41 PM, Esteban A. Maringolo <[email protected]>wrote: > This is where the "only 5 reserved keywords" stop being true :) > > I've been bitten by similar things and ended up using my own selectors, > sometimes with a prefix. > > Regards! > > Esteban A. Maringolo > > > 2014/1/21 Camille Teruel <[email protected]> > >> >> On 21 janv. 2014, at 17:53, Stephan Eggermont <[email protected]> wrote: >> >> I tried loading Deltawerken in Pharo 3.0 and noticed >> it is now impossible to load code where a class side method is defined >> named users. >> >> DEUser class>>users >> ^self subclassResponsibility >> >> Stephan >> >> >> I guess it's a consequence of the unification of Class and Trait APIs. >> Now SomeClass users must answer an empty collection. >> So you experience a name clash between Pharo meta-level and your domain :( >> I still think it was a mistake too push that unification that far, i.e >> having classes responding to trait specific methods and vice-versa. >> >> >
