> Am 18.07.2018 um 14:39 schrieb Damien Pollet <damien.pol...@gmail.com>: > > I understand what slots are, but haven't heard of frames in this context… can > you elaborate ? > +1
Norbert > On Wed, 18 Jul 2018 at 13:44, Reg Krock via Pharo-dev > <pharo-dev@lists.pharo.org <mailto:pharo-dev@lists.pharo.org>> wrote: > The Slot class implementation is fundamentally sound but the larger > constructs surrounding Frames and Slots still requires extensive thought. > > I suspect that you will find that many more changes will be discovered as > work is done with it. > > Slots provide the capacity to implement most of AOP concepts in a simple > manner. It also results in a Frame model. > > I also would suggest careful examination of when to use composition versus > traits with slots. > > Regards > > Reg Krock > > > > On 17 Jul2018, at 1:44 PM, Sean P. DeNigris <s...@clipperadams.com > > <mailto:s...@clipperadams.com>> wrote: > > > > teso...@gmail.com <mailto:teso...@gmail.com> wrote > >> the one that is disturbing, it is kept for > >> compatibility with the old behavior > > > > Are there enough users to justify backward compatibility if it costs a nice > > API? > > > > > > > > ----- > > Cheers, > > Sean > > -- > > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > > <http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html> > > > > > > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet > <http://people.untyped.org/damien.pollet>
