public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: gcc@gcc.gnu.org
Subject: Re: Making a struct field constant, when this struct is imported  	to a  particular Cpp files
Date: Thu, 12 Nov 2009 21:16:00 -0000	[thread overview]
Message-ID: <4AFC7EE6.7050208@gmail.com> (raw)
In-Reply-To: <20091112140302.GG22281@axel>

Axel Freyn wrote:
> Hi Ansis,
> 
> first: you should use gcc-help@gcc.gnu.org for questions like this...

  Indeed.  However, from the gcc@ point of view:

> Yes, this approach is save. 

  No, not remotely, and everyone on this list already knows why (or ought to
after a few moments thought, or else they're probably on the wrong list), so
I'll just point it out here for the record.  Anyone stumbling across this in
the archives can go check the reply on gcc-help(*) if they want a detailed
explanation.

    cheers,
      DaveK
-- 
(*) - http://gcc.gnu.org/ml/gcc-help/2009-11/msg00144.html

      reply	other threads:[~2009-11-12 21:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-12 13:45 ansis atteka
2009-11-12 14:03 ` Axel Freyn
2009-11-12 21:16   ` Dave Korn [this message]

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=4AFC7EE6.7050208@gmail.com \
    --to=dave.korn.cygwin@googlemail.com \
    --cc=gcc@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).