On 27 January 2017 at 01:30, Ben Coman <[email protected]> wrote: > On Fri, Jan 27, 2017 at 6:02 AM, stepharong <[email protected]> wrote: > > On Thu, 26 Jan 2017 20:38:49 +0100, Torsten Bergmann <[email protected]> > wrote: > > > >> stepharong wrote: > >>> > >>> can we rename this selector? > >>> asMethodConst should be at least be renamed to asConstantMethod > >> > >> > >> When you use "as {something}" then "something" depicts the result of the > >> conversion message sent to an object. > >> > >> Like in #asNumber or #asString which shows to what the receiver will be > >> converted. > > > > > > Yes I thought that it was doing that. > >> > >> > >> > >> My understanding is that in the case discussed the receiver object is > >> NOT converted to a constant unchangeable method, so #asConstantMethod > >> would > >> not fit as a selector. > >> > >> Instead it is sent to an object that afterwards is a constant within a > >> method > >> (so it will not be evaluated later at runtime again) so IMHO > >> #asMethodConstant > >> instead of #asMethodConst would be better. > > > > > > I do not understand any of them. > > method constant = constant of a method > constant method = method that does not change > > are you sure? maybe it is constant method = method that returns constant?
apparently, that's why 'constant' term doesn't fits there, because there's so many confusion about it. what are the constant in dynamic system, after all? HTH, cheers -ben > > -- Best regards, Igor Stasenko.
