Ticket #795 (closed RFC: done)

Opened 13 years ago

Last modified 12 years ago

Kill Parrot_sub structure

Reported by: whiteknight Owned by: bacek
Priority: normal Milestone:
Component: core Version: 1.3.0
Severity: medium Keywords: pmc
Cc: Language:
Patch status: Platform:

Description (last modified by bacek) (diff)

The Sub PMC has a single attribute, a Parrot_sub structure. Likewise, the Continuation PMC has a Parrot_cont structure as an attribute. I suggest that we should kill these structures and store their members as ATTRs directly in the PMC. Are there any reasons why this would be a bad idea?

(Parrot_continuation now tracked in #926)

Change History

Changed 13 years ago by allison

It's an excellent idea, a good second stage in the PMC cleanup. (At the time Sub and Continuation were developed, PMCs didn't have ATTRs.)


Changed 13 years ago by jkeenan

  • component changed from none to core

Changed 12 years ago by bacek

  • owner set to bacek


I'll take Sub PMC and split separated ticket for Continuation PMC.

-- Bacek

Changed 12 years ago by bacek

  • description modified (diff)
  • summary changed from Kill Parrot_sub and Parrot_cont structures to Kill Parrot_sub structure

Changed 12 years ago by bacek

  • status changed from new to closed
  • resolution set to done

Branch for killing Parrot_sub structure was merged into trunk.

Note: See TracTickets for help on using tickets.