linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Glynn Clements <glynn@gclements.plus.com>
Cc: C programming list <linux-c-programming@vger.kernel.org>
Subject: Re: pointer indirection on the LHS of an assignment
Date: Sun, 8 Oct 2006 02:53:46 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0610080252420.12188@localhost.localdomain> (raw)
In-Reply-To: <17704.12250.231544.173434@cerise.gclements.plus.com>

On Sat, 7 Oct 2006, Glynn Clements wrote:

>
> Robert P. J. Day wrote:
>
> >   sort of a combination of a C and gcc question but what's the rules
> > these days on the following (ripped from the linux kernel source, from
> > asm/semaphore.h)?
> >
> > ===
> > static inline void sema_init (struct semaphore *sem, int val)
> > {
> > /*
> >  *      *sem = (struct semaphore)__SEMAPHORE_INITIALIZER((*sem),val);
> >  *
> >  * i'd rather use the more flexible initialization above, but sadly
> >  * GCC 2.7.2.3 emits a bogus warning. EGCS doesn't. Oh well.
> >  */
> >         atomic_set(&sem->count, val);
> >         sem->sleepers = 0;
> >         init_waitqueue_head(&sem->wait);
> > }
> > ===
> >
> >   i recall that earlier compilers complained about that first example
> > of pointer indirection as the target of an assignment.  is that legal
> > these days?
>
> The problem with the first example is that the
> __SEMAPHORE_INITIALIZER macro uses C99 features, which probably
> aren't supported in gcc 2.7.x.
>
> The LHS has nothing to do with it.

ah, sorry, i didn't look closely enough.  so if one could count on a
C99-compilant compiler being available, then the first form would be
perfectly acceptable?  thanks.

rday

  reply	other threads:[~2006-10-08  6:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-07 13:12 pointer indirection on the LHS of an assignment Robert P. J. Day
2006-10-07 22:53 ` Glynn Clements
2006-10-08  6:53   ` Robert P. J. Day [this message]
2006-10-08 12:17     ` Glynn Clements

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=Pine.LNX.4.64.0610080252420.12188@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=glynn@gclements.plus.com \
    --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).