public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Csaba Raduly <rcsaba@gmail.com>
To: cygwin list <cygwin@cygwin.com>
Subject: Re: [64bit] cygwin-devel headers broken
Date: Sat, 02 May 2015 17:38:00 -0000	[thread overview]
Message-ID: <CAEhDDbCyLRY3PRjhWqgsW25-Dez2pmJ9KZOexXEKwFwtTXxXzg@mail.gmail.com> (raw)
In-Reply-To: <CAOC2fq_4n_AXbTCEzL0herVbHhQ_mC=somEnhv-=mduiRnKWBw@mail.gmail.com>

On Fri, May 1, 2015 at 9:29 PM, Michael Enright  wrote:
> When changing from compiler to compiler, even if it be just an OS
> point version upgrade, implicit header inclusions go away all the
> time. As a developer, I just shrug this off as one of the trade-offs
> of choosing to develop in C or C++, which lack proper module systems.
(snip)

Please don't top-post.

No need for a trade-off. Include-what-you-use (
http://code.google.com/p/include-what-you-use/ )
will tell exactly which headers are needed, so there's no need to rely
on which header includes which.

Csaba
-- 
GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++
The Tao of math: The numbers you can count are not the real numbers.
Life is complex, with real and imaginary parts.
"Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds
"People disagree with me. I just ignore them." -- Linus Torvalds

--
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:[~2015-05-02 17:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30 18:52 Thomas Wolff
2015-05-01  5:03 ` Marco Atzeri
2015-05-01 12:10   ` Jon TURNEY
2015-05-01 18:19     ` Thomas Wolff
2015-05-01 20:12       ` Michael Enright
2015-05-02 17:38         ` Csaba Raduly [this message]
2015-05-01 20:23       ` Marco Atzeri
2015-05-01 20:38         ` Eric Blake
2015-05-02 13:38           ` Corinna Vinschen
2015-05-01 20:25     ` J. Offerman

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=CAEhDDbCyLRY3PRjhWqgsW25-Dez2pmJ9KZOexXEKwFwtTXxXzg@mail.gmail.com \
    --to=rcsaba@gmail.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).