home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.misc
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!iggy.GW.Vitalink.COM!cs.widener.edu!eff!news.byu.edu!hamblin.math.byu.edu!hellgate.utah.edu!lanl!cochiti.lanl.gov!jlg
- From: jlg@cochiti.lanl.gov (J. Giles)
- Subject: Re: Pointers
- Message-ID: <1992Nov13.225059.17616@newshost.lanl.gov>
- Sender: news@newshost.lanl.gov
- Organization: Los Alamos National Laboratory
- References: <BxJzzv.4H7@mentor.cc.purdue.edu> <721539019@sheol.UUCP> <1992Nov12.203014.11596@newshost.lanl.gov> <BxnrI0.10M@mentor.cc.purdue.edu>
- Date: Fri, 13 Nov 1992 22:50:59 GMT
- Lines: 18
-
- In article <BxnrI0.10M@mentor.cc.purdue.edu>, hrubin@pop.stat.purdue.edu (Herman Rubin) writes:
- |> [...]
- |> Even if you have the greater capablility, do you have to insist on
- |> making things complicated by using it? [...]
-
- Frankly, I find much of your code very difficult to follow
- because pointers make the thing more complicated than it needs
- to be. I don't need the address of the function. Therefore,
- I don't need a variable whose explicit semantics is that it
- holds such an address, and I actually don't *want* to have to
- `dereference' the thing to get the semantics I really *do*
- want. The very fact I need a dereferencing operator in C and
- I wouldn't if functions were first-class objects is a clear
- demonstration that the pointer implementation is *more*
- complicated from the user's perspective.
-
- --
- J. Giles
-