in reply to Re^3: [perl6] Complex Attribute Validation and/or Triggers (anti-modular)
in thread [perl6] Complex Attribute Validation and/or Triggers

I almost didn't post in this thread precisely because the initial #perl6 reaction was "what tye said" (referencing your initial just-write-a-method response). I'm pretty sure they'd say the same of this follow up, but I'll add :

public attributes are a bad idea

Indeed. There are no public (or even protected) attributes in Perl 6 OO, only private. Code that uses objects, and even sub, super, and trusted classes, has to go thru method accessors.

Update Fwiw, on reviewing this thread I'm pretty sure I missed tye's point. I'm right that Perl 6 doesn't have "public attributes" using Perl 6 vocabulary. But (I think) tye meant that even public accessor methods are generally a bad idea (no matter what language one is using).

  • Comment on Re^4: [perl6] Complex Attribute Validation and/or Triggers (anti-modular)