On Thu, May 19, 2011 at 01:40:39PM -0000, Parrot wrote: > Comment(by whiteknight): > > I knew Rakudo was using it, I wasn't sure to what extent. I'm glad to hear > it is more commonly used (and without any major problems). > > I would still like to change getprop_p_s_p to getprop_p_p_s.
This should be no problem -- add getprop_p_p_s now, give clients (like Rakudo) a supported release or two to make the switch, then eliminate getprop_p_s_p. FWIW, getprop's inconsistent with other ops has always struck me as odd as well, so I'm fine with the proposed change. > As a follow-up, does this property system work as well as you would like > it to? Are there any changes you could suggest? If we're talking about a > major overhaul of the object model to begin sooner than later, object > properties is something we could get right if it isn't already right. We probably won't know entirely until we have Rakudo completely switched over to the new system, although Jonathan might have some insights to share here. Pm _______________________________________________ parrot-tickets mailing list [email protected] http://lists.parrot.org/mailman/listinfo/parrot-tickets
