On Jun 16, 2006, at 17:29, Klaas-Jan Stol wrote:
Wouldn't it be an idea to have a property 'is_read_only' or something like that? Then, when attempting to do a write action on a r/o PMC, an exception is thrown. It would seem to me that this is a typical case for using a property.
A "Parrot property" is handled by a full-fledged hash and by far too heavy to serve the information of a single bit 'r/o'. "Perl6 properties" will be (according to docs) implemented by (possibly singleton) classes.
For the subject, just swapping vtables is enough, which doesn't impose any runtime overhead to check for r/o-ness. We will still need some infrastructure and thoughts, how to manage additional vtables per type.
leo
