public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin's GCC doesn't like this .sa_handler initialization for  some reason
Date: Tue, 27 Apr 2010 14:54:00 -0000	[thread overview]
Message-ID: <20100427145400.GA14300@trixie.casa.cgf.cx> (raw)
In-Reply-To: <4BD6F290.3020404@redhat.com>

On Tue, Apr 27, 2010 at 08:20:00AM -0600, Eric Blake wrote:
>On 04/27/2010 08:06 AM, Corinna Vinschen wrote:
>>> And while we're touching the file, we probably want to do similar
>>> treatment for struct siginfo_t: si_tid, si_overrun, si_sigval, si_value,
>>> si_status, si_utime, si_stime, and si_addr.
>> 
>> Does "we" mean you're going to provide a patch?
>
>Yes.  Patch coming up shortly.

Wait.

This is not the first time that this kind of issue has come up.  I am extremely
loath to stop using anonymous unions.  So much so in fact, that I don't really
care that this makes us slightly incompatible with Linux.

Polluting the namespace like this is just ugly.  I'd rather not do it.  I'd
rather tell the handful of applications which have problems with this that this
is an incompatibility.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2010-04-27 14:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100425113232.GA11541@sbox>
2010-04-26 16:45 ` Eric Blake
2010-04-26 18:35   ` Dave Korn
2010-04-27  9:05     ` Corinna Vinschen
2010-04-27 13:58       ` Eric Blake
2010-04-27 14:06         ` Corinna Vinschen
2010-04-27 14:20           ` Eric Blake
2010-04-27 14:54             ` Christopher Faylor [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=20100427145400.GA14300@trixie.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@cygwin.com \
    --cc=cygwin@cygwin.com \
    /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).