Brian Lloyd wrote:
> Yes - basically any class that defines *or inherits from a
> class that defines* permissions should do this to make sure
> that the permissions along the inheritance heirarchy are
> cobbled together correctly at class initialization time.
I'm sure someone said recently that t
> >
> > Are you calling:
> >
> > Globals.default__class_init__(MyBasketClass)
> >
> > on your Basket class? This is (poorly documented but)
> > necessary for permissions declared in __ac_permissions__
> > to be correctly initialized.
>
> Should I have this in Squishdot too?
>
> Chris
Yes - b
Brian Lloyd wrote:
>
> > So, what do I need to do to allow controlled access to this object?
> > I understand that Shopper, inheriting from SimpleItem, already has
> > the access to unprotected subobjects flag. And I'd rather protect
> > the object correctly, anyway . I tried adding an ac_permi
On Fri, 7 Jul 2000, Brian Lloyd wrote:
> Are you calling:
>
> Globals.default__class_init__(MyBasketClass)
>
> on your Basket class? This is (poorly documented but)
> necessary for permissions declared in __ac_permissions__
> to be correctly initialized.
Poorly?
Only three classes seem to u
> So, what do I need to do to allow controlled access to this object?
> I understand that Shopper, inheriting from SimpleItem, already has
> the access to unprotected subobjects flag. And I'd rather protect
> the object correctly, anyway . I tried adding an ac_permissions
> structure to the clas