It is rather annoying that attributes don't JFW everywhere, yes. I do
wish, in general, that ParrotClass and PMC had more in common.
I'm not sure how I'm to access these via PIR: I get the same
src/objects.c:1452: failed assertion `(class)->pmc_ext'
error after applying this patch.
I'm going
The problem is that a Sub is not a ParrotObject, so it has nowhere to
store attributes. That's why attr_str_2_num throws "Can't set
non-core object attribs": it can't safely use PMC_data unless you've
passed a ParrotObject. I've attached a patch that implements a basic
attribute storage system f
