For compatiblity with Pharo, Trait definition must write an optional category and packageName to disk ...

[dalehenrich]

Category is not required and the packageName will not be stored as an attribute, but derived from the name of the package the definition is in ...

For strict compatibility for Pharo, the packageName and category are expected to match(?) ...

For GemStone, the category and packageName are not required ...

Related to internal issue "51233 P3 generategs with traits has confusing interpretation of Trait category"

spec_0084 and spec_0085 are incomplete with respect to Pharo compatibility for Rowan:masterV3.2.

Moving forward spec_0086, spec_0087 and spec_0088 will be the primary examples for Traits.

[dalehenrich]

The implementation of Traits in Rowan3 in branch masterV3.2 was incomplete with respect to Pharo compatibility (namely category and packageName properties in the Trait definition).

For Pharo compatility if a category is defined for a Trait, then the packageName for the Trait will be written to disk.

GemStone and Rowan V3 will ignore a packageName property for a Trait when read (the name of the containing package will be used) and the category property is optional - standard default category ('Kernel'/'User Classes') name used for classes should apply)