in reply to managing object permissions
.oO(I'm sure I'm teaching my granny to suck eggs, but here goes anyway...)
As far as hierarchy is concerned, why not fall back on the inheritance of methods, accessors & mutators e.g. in your example, Desk->method() resulting in Workflow->method() actually being the method called - thus indirectly implementaing the inheritance of permissions etc. e.g.
etc. etc.package Workflow; sub method { my $self = shift; . . . } package Desk; use base qw/Workflow/; sub new { bless \( my $scalar ), ref $_[0] || $_[0] } package main; my $desk = Desk->new(); $desk->method();
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: managing object permissions
by LanX (Saint) on Nov 26, 2008 at 17:36 UTC | |
by Bloodnok (Vicar) on Nov 26, 2008 at 18:26 UTC |