home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!pacsoft!mike
- From: mike@pacsoft.com (Mike Stefanik)
- Newsgroups: comp.lang.c
- Subject: Re: Why should POINTERS be so damn hard to understand ?
- Message-ID: <1363@pacsoft.com>
- Date: 29 Aug 92 21:07:32 GMT
- References: <l9nl34INNhln@almaak.usc.edu> <25233@castle.ed.ac.uk> <1992Aug27.135946.6622@infonode.ingr.com>
- Organization: Pacific Software Group, Riverside, Ca.
- Lines: 13
-
- In an article, henders@infonode.ingr.com (Greg Henderson) writes:
- >[...] if you are worried about low-level efficiency the second
- >version [using a pointer] is a little tighter, as each reference
- >to the array value in the pointer version requires less work to
- >come up w/ that address.
-
- This depends on which machine and what compiler you're using... I've
- seen code using array indices run faster than the flavor using pointers.
- Efficiency is a subjective thing after all, and it doesn't necessarily
- mean just making the program run faster.
- --
- Mike Stefanik mike@pacsoft.com ...!uunet!pacsoft!mike
- Pacific Software Group, Riverside, CA
-