But for caching you have a cache. The whole point of memoization support is to have it easy to do. Look at the bottom of this page: http://wiki.tcl.tk/10981
So if we could have some kind of the same using manipulation of thisContext and/or Slots, it would be nicer. e.g. SomeClass>>#initialize self memoize: #someMethod:andParms:. and bingo, automatic method memoization keyed by the objects passed. That would be better. Phil On Thu, Jan 26, 2017 at 12:20 AM, Igor Stasenko <siguc...@gmail.com> wrote: > > > On 26 January 2017 at 01:14, p...@highoctane.be <p...@highoctane.be> > wrote: > >> If one is doing any dynamic programming, the memoization term is pretty >> natural. >> >> for that purpose, i naturally using 'caching' wording. > > >> https://youtu.be/OQ5jsbhAv_M?t=3m11s >> >> Phil >> >> On Wed, Jan 25, 2017 at 10:30 PM, Igor Stasenko <siguc...@gmail.com> >> wrote: >> >>> #once can be interpreted as 'evaluate it once', >>> >>> but i don't like the #memoized .. it sounds painful to my ears. >>> It sounds like something stinking smeared across my face.. and i always >>> got stuck,confused and lost as the meaning of it always >>> escaping my mind, since it naturally defends itself from any unpleasant >>> thoughts. >>> >>> IMHO, maybe #once is not the best wording for what it does , but >>> #memoizing... yuck.. pardon me. >>> >>> :) >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko. >>> >> >> > > > -- > Best regards, > Igor Stasenko. >
