#218: can't sort a PIR subclass of an RPA.
--------------------+-------------------------------------------------------
 Reporter:  coke    |        Owner:  whiteknight
     Type:  bug     |       Status:  reopened   
 Priority:  normal  |    Milestone:             
Component:  core    |      Version:             
 Severity:  fatal   |   Resolution:             
 Keywords:          |         Lang:             
    Patch:          |     Platform:  all        
--------------------+-------------------------------------------------------

Comment(by coke):

 This ticket has a deprecation notice with it that says:

 {{{
 These opcodes are being repurposed. They will always return a unique
 memory
 address of the PMC. Uses of get_addr and set_addr that would set label
 values
 for Sub, Exception, and related PMC types will instead be handled by
 get_label and set_label.
 }}}

 But allison states earlier in the thread

 {{{
 We don't really want to provide a way to get at the raw memory address of
 a PMC from PIR, because we want a copying/compacting garbage collector,
 which means the memory address can change. PIR code that relies on a
 consistent memory address for a PMC is broken.
 }}}

 So, it sounds like this is a rejection of the task listed in
 deprecated.pod. Can we get a ruling on that? (And if yes, open a new
 ticket and point to that one for the deprecation notice instead. The
 original problem in this ticket is resolved.)

-- 
Ticket URL: <https://trac.parrot.org/parrot/ticket/218#comment:28>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets

Reply via email to