[e-lang] An object-capability subset of Python

Ben Laurie benl at google.com
Sat Aug 16 09:31:22 CDT 2008


On Fri, Aug 15, 2008 at 8:00 PM, Mark Seaborn <mrs at mythic-beasts.com> wrote:
> "Ben Laurie" <benl at google.com> wrote:
>> In CaPerl I did run-time checking.
>
> I don't think it will be necessary to insert run-time checks in
> CapPython.  CapPython uses the "same-object" meaning of "private" (as
> in E) rather than the "same-class" meaning (as in Java).  This means
> the ability to access private attributes can be determined
> syntactically.

OK, then I don't understand how CapPython works...

> CaPerl uses "same-class"/"same-module" private [1], so it needs to do
> run-time checks.

Yes, that's actually a weakness in CaPerl. Perhaps I should revisit it
and try to make it work properly.


More information about the e-lang mailing list