Xref: utzoo comp.lang.eiffel:1383 comp.object:2522
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!mips!daver!tscs!tct!chip
From: chip@tct.uucp (Chip Salzenberg)
Newsgroups: comp.lang.eiffel,comp.object
Subject: Re: read_only type classification (was: Inheritance and Information Hiding)
Message-ID: <27B0742F.B01@tct.uucp>
Date: 6 Feb 91 21:25:03 GMT
References: <1991Feb1.015749.10111@Neon.Stanford.EDU> <1081@tetrauk.UUCP> <1991Feb5.204144.26857@cs.ucla.edu>
Organization: Teltronics/TCT, Sarasota, FL
Lines: 12

>In article <1081@tetrauk.UUCP>, rick@tetrauk.UUCP (Rick Jones) writes:
> Has anyone tried to address this problem by considering that a class
> essentially has two interfaces?  One - the "read" interface - provides
> information about the object in its current (abstract) state.  The other
> - the "write" interface - offers facilities to change the object.

Correct me if I'm wrong, but I believe that the C++ |const| modifier
already provides this feature.  Or is something missing?
-- 
Chip Salzenberg at Teltronics/TCT     <chip@tct.uucp>, <uunet!pdn!tct!chip>
 "Most of my code is written by myself.  That is why so little gets done."
                 -- Herman "HLLs will never fly" Rubin