Xref: utzoo comp.lang.eiffel:1380 comp.object:2518
Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!think.com!sdd.hp.com!usc!apple!cambridge.apple.com!alms
From: alms@cambridge.apple.com (Andrew L. M. Shalit)
Newsgroups: comp.lang.eiffel,comp.object
Subject: Re: read_only type classification (was: Inheritance and Information Hiding)
Message-ID: <ALMS.91Feb6144137@ministry.cambridge.apple.com>
Date: 6 Feb 91 19:41:37 GMT
References: <10612@pasteur.Berkeley.EDU> <485@eiffel.UUCP> <488@eiffel.UUCP>
	<1991Feb1.015749.10111@Neon.Stanford.EDU> <1081@tetrauk.UUCP>
	<1991Feb5.204144.26857@cs.ucla.edu>
Sender: news@cambridge.apple.com
Organization: Apple Computer Inc, Cambridge, MA
Lines: 14
In-reply-to: rowley@bath.cs.ucla.edu's message of 5 Feb 91 20:41:44 GMT

In article <1991Feb5.204144.26857@cs.ucla.edu> rowley@bath.cs.ucla.edu (Michael T Rowley) writes:

   My understanding of the usage of the read_only specification with
   the RECTANGLE/POLYGON example:

   - RECTANGLE would inherit from "read_only POLYGON"

Um...  What if you want to change the size of the rectangle?

Just because one attribute is read-only, doesn't mean all the
other ones are going to be read-only as well.

   -andrew
--