Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
| From | "Bill Cunningham" <nospam@nspam.invalid> |
|---|---|
| Newsgroups | comp.lang.c |
| Subject | Re: pointers and pointing |
| Date | 2014-04-22 14:09 -0400 |
| Organization | A noiseless patient Spider |
| Message-ID | <lj6b9d$dn1$1@dont-email.me> (permalink) |
| References | (1 earlier) <rfqal9lmqc2a7i1kcs7s6laug96jd4p2to@4ax.com> <lj45rt$cca$1@dont-email.me> <mtpbl9t2ahpbmc14ipu0i2a0uu91dvgbdq@4ax.com> <lj5ran$hea$1@dont-email.me> <lj5up1$bfj$1@dont-email.me> |
Ken Brody wrote:
> On 4/22/2014 9:37 AM, Bill Cunningham wrote:
> [...]
>> int *p;
>>
>> Ok when do I use p and when do I use *p. That right now I am working
>> on.
>
> If "p" is a pointer, you use "p" when you want the pointer, and "*p"
> when you want what it points to. (And you use "&p" when you want to
> point to the pointer.)
I understood that much. But I think some of the problem with this here
is documentation for certain functions. Docs don't always do well in
explaining what a function wants. Seeing a parameter wants a generic pointer
can mean it wants p or *p or &p. Just depending on the function of the
function. And with a parameter that says void * makes things even worse
because it is written to take any type. I am speaking of getaddrinfo() in
particularly. It deals with struct addrinfo type.
WIth this one mentioned above, you better understand what this function
is all about.
Bill
Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
pointers and pointing "Bill Cunningham" <nospam@nspam.invalid> - 2014-04-21 13:57 -0400
Re: pointers and pointing Barry Schwarz <schwarzb@dqel.com> - 2014-04-21 11:58 -0700
Re: pointers and pointing "Bill Cunningham" <nospam@nspam.invalid> - 2014-04-21 15:09 -0400
Re: pointers and pointing buja <buja66@gmail.com> - 2014-04-21 12:44 -0700
Re: pointers and pointing gazelle@shell.xmission.com (Kenny McCormack) - 2014-04-21 20:28 +0000
Re: pointers and pointing "Osmium" <r124c4u102@comcast.net> - 2014-04-21 15:43 -0500
Re: pointers and pointing Ken Brody <kenbrody@spamcop.net> - 2014-04-22 10:28 -0400
Re: pointers and pointing ralph <nt_consulting@yahoo.com> - 2014-04-21 16:25 -0500
Re: pointers and pointing Barry Schwarz <schwarzb@dqel.com> - 2014-04-21 15:14 -0700
Re: pointers and pointing James Kuyper <jameskuyper@verizon.net> - 2014-04-21 18:41 -0400
Re: pointers and pointing gazelle@shell.xmission.com (Kenny McCormack) - 2014-04-21 22:48 +0000
Re: pointers and pointing jacob navia <jacob@spamsink.net> - 2014-04-22 00:22 +0200
Re: pointers and pointing "Bill Cunningham" <nospam@nspam.invalid> - 2014-04-21 18:25 -0400
Re: pointers and pointing Barry Schwarz <schwarzb@dqel.com> - 2014-04-21 20:56 -0700
Re: pointers and pointing glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2014-04-22 05:51 +0000
Re: pointers and pointing James Kuyper <jameskuyper@verizon.net> - 2014-04-22 07:38 -0400
Re: pointers and pointing David Brown <david.brown@hesbynett.no> - 2014-04-22 09:16 +0200
Re: pointers and pointing "Bill Cunningham" <nospam@nspam.invalid> - 2014-04-22 09:37 -0400
Re: pointers and pointing Richard <rgrdev_@gmail.com> - 2014-04-22 15:00 +0100
Re: pointers and pointing Ken Brody <kenbrody@spamcop.net> - 2014-04-22 10:36 -0400
Re: pointers and pointing "Bill Cunningham" <nospam@nspam.invalid> - 2014-04-22 14:09 -0400
Re: pointers and pointing Ben Bacarisse <ben.usenet@bsb.me.uk> - 2014-04-22 22:40 +0100
Re: pointers and pointing Richard <rgrdev_@gmail.com> - 2014-04-23 00:05 +0100
Re: pointers and pointing Barry Schwarz <schwarzb@dqel.com> - 2014-04-22 16:08 -0700
Re: pointers and pointing "Bill Cunningham" <nospam@nspam.invalid> - 2014-04-23 22:19 -0400
Re: pointers and pointing "Bill Cunningham" <nospam@nspam.invalid> - 2014-04-22 14:22 -0400
Re: pointers and pointing "Bill Cunningham" <nospam@nspam.invalid> - 2014-04-22 14:24 -0400
Re: pointers and pointing buja <buja66@gmail.com> - 2014-04-22 13:12 -0700
csiph-web