> Reading through the updated code, it seems that (using "Task" as an > example): > > Parrot_PMCdata_Task > > is not much clearer than the original "Parrot_Task" was. Let's go with: > > Parrot_Task_attributes
A fast ack'ing of: Parrot_[_a-zA-Z]+_attributes for possible collisions shows only: Parrot_Class_nci_attributes Parrot_Role_nci_attributes We can live with this. > (Fortunately, with the string "PMCdata" in all the type names, it should be > easy to write an automatic search-and-replace.) That was the main reason for using a long ugly name. -- Salu2
