Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| Language design: exposed and read only... nfactorial@btopenworld.com (n!) (2002-10-13) |
| Re: Language design: exposed and read only... kgw-news@stiscan.com (2002-10-18) |
| From: | kgw-news@stiscan.com |
| Newsgroups: | comp.lang.misc,comp.compilers |
| Date: | 18 Oct 2002 23:26:08 -0400 |
| Organization: | Solution Technology |
| References: | 02-10-034 |
| Keywords: | design |
| Posted-Date: | 18 Oct 2002 23:26:08 EDT |
On Sun, 13 Oct 2002 20:35:54 UTC, "n!" <nfactorial@btopenworld.com> wrote:
> [In my new langugage] one thing I've
> been thinking about is access privilege levels for class members.
>
> I was thinking along the lines of the following:
>
> private access, members are not accessible from anything outside of its
> owning object. This includes objects of the same type. So for example:
Yes, but is it useful? After all, the implementor can/would always
change it to suite the implementation. It would be just another
bothersome detail with little to gain for it.
Return to the
comp.compilers page.
Search the
comp.compilers archives again.