#2114: getprop op is strange
-------------------------+--------------------------------------------------
Reporter: whiteknight | Owner:
Type: RFC | Status: new
Priority: trivial | Milestone:
Component: core | Version: master
Severity: low | Keywords:
Lang: | Patch:
Platform: all |
-------------------------+--------------------------------------------------
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. That's a
small, low-priority aesthetic nit, but I wanted to keep track of the issue
anyway. I marked this ticket "trivial" when I created it, so nobody needs
to get worried about this quite yet.
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.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/2114#comment:2>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
