home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cis.ohio-state.edu!zaphod.mps.ohio-state.edu!cs.utexas.edu!sun-barr!ames!data.nas.nasa.gov!taligent!apple!netcomsv!spacebbs!ted.jensen
- From: ted.jensen@spacebbs.com (Ted Jensen)
- Newsgroups: comp.lang.c
- Subject: Re: Pointer/address
- Message-ID: <10680.610.uupcb@spacebbs.com>
- Date: 28 Aug 92 14:36:00 GMT
- Reply-To: ted.jensen@spacebbs.com (Ted Jensen)
- Distribution: na
- Organization: SPACE BBS - Menlo Park, CA - 10 Lines + 4gB - 415-323-4193
- Lines: 35
-
-
-
- steve@taumet.com (Steve Clamage) writes (in answer to my article)
-
- TJ>Thus I think that by virtue of the fact that we have two
- TJ>different words for describing the a variable type (pointer) and
- TJ>the contents stored in such a variable type (address) a
- TJ>description of what is actually taking place when using pointers
- TJ>_can_, in a sense, be made clearer than when using integers or
- TJ>floats.
-
- > Finally, a pointer variable need not contain a machine address.
- > It might contain more than an address, as on capability
- > architectures, or less than an address, as on some segmented
- > architectures, or something which only describes an address, as
- > when part of the pointer is an index into a table of segments or
- > addresses.
-
- Finally! I have posted my reasons for preferring the use of
- "address" over "pointer" in certain contexts many times on
- various BBS's. I have often received criticism based on the fact
- that virtually no author (including of course the ANSI standard,
- K&R1, and K&R2) was in agreement with me. That, in itself, would
- not make my usage incorrect IMHO. None of the books I have ever
- seen have been explicit about why their phrasing was preferred or
- even correct. However, here, finally, you have clearly and
- explicitly stated why my usage of "address" was incorrect.
-
- I bow to your more reasonable explanation and thank you for
- pointing out my error.
-
- Ted Jensen
- ---
- * SLMR 2.0 *
-
-