linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Glynn Clements <glynn@gclements.plus.com>
To: gumbold@bonbon.net
Cc: linux-c-programming@vger.kernel.org
Subject: Re: data structure question
Date: Tue, 17 May 2005 08:36:40 +0100	[thread overview]
Message-ID: <17033.40712.26126.544056@gargle.gargle.HOWL> (raw)
In-Reply-To: <4288E71C.2060400@bonbon.net>


gumbold wrote:

> > then sizeof(struct abc) would be 8 and the offset of abc from the
> > beginning of the structure would be 4.
> > 
> > With:
> > 
> > 	struct abc {
> > 	    __u16 a;
> > 	    __u16 b;
> > 	    char abc[0];
> > 	};
> > 
> > sizeof(struct abc) would be 4 and the offset of abc from the beginning
> > of the structure would still be 4 (i.e. p->abc refers to the first
> > byte after the structure).
> 
> I understand. But if you doing `p->abc = (char *)malloc(111)'

That would be an error. p->abc is an array, not a pointer.

Arrays and pointers aren't the same. They are often confused, for
several reasons:

1. An array is automatically converted to a pointer to its first
element whenever it occurs as an expression. This doesn't apply to
lvalues (e.g. in declarations or as the argument to sizeof).

2. In a declaration, the syntax foo[...] declares an array named foo,
but in the expression foo[...], foo is a pointer (it might be an array
which has been converted to a pointer according to point 1 above, but
it's still a pointer).

3. In a function prototype, pointer arguments can be declared using
either "T foo[]" or "T *foo".

-- 
Glynn Clements <glynn@gclements.plus.com>

  reply	other threads:[~2005-05-17  7:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-15  9:32 data structure question gumbold
2005-05-15 11:02 ` Glynn Clements
2005-05-15 11:24   ` gumbold
2005-05-15 14:23     ` Glynn Clements
2005-05-16  4:00       ` gumbold
2005-05-16 15:28         ` Glynn Clements
2005-05-16 18:31           ` gumbold
2005-05-17  7:36             ` Glynn Clements [this message]
2005-05-16 19:07           ` gumbold

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=17033.40712.26126.544056@gargle.gargle.HOWL \
    --to=glynn@gclements.plus.com \
    --cc=gumbold@bonbon.net \
    --cc=linux-c-programming@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).