[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Is there any approach to define "private" vars in GOOPS?

From: Mark H Weaver
Subject: Re: Is there any approach to define "private" vars in GOOPS?
Date: Wed, 09 Mar 2011 04:46:31 -0500
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux)

There is another approach (probably overkill) to storing private
attributes of GOOPS objects, or any other Scheme object for that matter:
Weak-key hash tables, documented in section of the manual.
A nice high-level interface for using them is `make-object-property'.

However, it should be noted that Guile doesn't attempt to enforce strong
security barriers within a single process.  Even non-exported interfaces
in a module can be accessed from outside using the (@@ MODULE VAR)
syntax (section 6.19.2).


Neil Jerram <address@hidden> writes:
> However, the module system can't prevent any code from doing
>  (slot-ref obj 'some-slot-that-should-be-private)
> once it has OBJ, and knows that OBJ has a slot named
> some-slot-that-should-be-private.
> (In effect because slot names live in a different namespace from that of
> identifiers, and which isn't connected to the module system.)
> If you can determine at runtime whether or not any given slot access is
> allowed - perhaps based on (current-module) - it should be possible to
> enforce this by defining a new kind of slot #:allocation and putting
> that runtime check in the #:slot-ref function.
> Regards,
>         Neil

reply via email to

[Prev in Thread] Current Thread [Next in Thread]