The language you are thinking of is most probably PHANtom: http://pleiad.cl/phantom But (as author of the language) I think it is overkill to use it for just a memoization cache. Idem for AspectS (I don’t know if it works on Pharo though). Right now, I would use MethodWrappers instead, and when Reflectivity is working use that.
On Nov 4, 2014, at 1:50 PM, Denis Kudriashov <dionisi...@gmail.com> wrote: > Hi > > There is AspectS package at old squeaksource site. I not know is it working > in Pharo. > And there was presentation at Esug few years ago about another implementation > of aspects in Pharo ( i not remember project name) > > 04 нояб. 2014 г. 9:04 пользователь "p...@highoctane.be" <p...@highoctane.be> > написал: > > Le 3 nov. 2014 22:13, "Hilaire" <hila...@drgeo.eu> a écrit : > > > > What's wrong with? > > > > myData > > ^ data ifNil: [data := self computeMe] > > That I do have a lot of places like this and do not want these data littering > the code. > > Aspects would solve this but we do not have that. > > Also I need the mechanism to be removable. > > So, I read something about MethodWrapper, ghost, slots... Can't one use any > of these things to do this memoization cleanly? > > Phil > > > > > > > > > Le 03/11/2014 16:10, p...@highoctane.be a écrit : > > > How can I do memoization in Pharo? > > > > > > I mean, a generic mechanism that will help me wrap the caching around > > > the method invocations / messages. > > > > > > I have expensive calls that do not have to refresh their results as > > > often as they are called. > > > > > > TIA > > > Phil > > > > > > -- > > Dr. Geo - http://drgeo.eu > > iStoa - http://istoa.drgeo.eu > > > > > > ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile
