[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Access protection
- To: Nat Ballou <ballou@ernest.aca.mcc.com>
- Subject: Re: Access protection
- From: "dsr@luke.mitre.org"@mbunix.mitre.org (Douglas S. Rand)
- Date: Thu, 15 Mar 90 11:19:21 EST
- Cc: commonloops.pa@Xerox.COM, dsr@mbunix.mitre.org
- In-reply-to: Your message of Thu, 15 Mar 90 08:47:00 -0600. <19900315144735.5.BALLOU@LILITH.ACA.MCC.COM>
- Posted-from: The MITRE Corp., Bedford, MA
- Redistributed: commonloops.pa
It's important to separate two entirely different issues. There are two
features to C++. The first feature is some support for object oriented
programming. The second feature is basically data abstraction or data
hiding. OOP does not automatically include the second feature.
In particular the LISP environment is one where people often hack around and
nearly every manipulation is possible. This said there is an answer to
the (setf foo) problem. Instead of declaring the slot with
:accessor foo you declare it with :reader foo and no setf function is
generated. I'm not sure what, if anything, will happen in a WITH-SLOTS
form if you use SETF.
Cheers,
Doug <dsrand@mitre.org>