From: Joe Buck <jbuck@synopsys.com>
To: rth@cygnus.com
Cc: egcs@cygnus.com
Subject: Re: egcs-1.0.3a on DEC Alpha / DU4.0b: typedef of ulong in types.h
Date: Mon, 20 Jul 1998 12:20:00 -0000 [thread overview]
Message-ID: <199807201609.JAA00421@atrus.synopsys.com> (raw)
In-Reply-To: <19980718134803.A6256@dot.cygnus.com>
> On Thu, Jul 16, 1998 at 05:47:31PM -0700, Joe Buck wrote:
> > Does/should fixinclude try to fix Posix violations, or only ANSI/ISO
> > violations? (I suppose it can't do it in general since many gcc targets
> > aren't really Posix).
>
> No, that way lies madness. I'm actually surprised we do what we do
> with fixincludes, instead of coping out and stating that you only get
> an ISO environment if the vendor provides one.
That copout would have meant "no gcc on SunOS4 unless you buy Sun's
proprietary ANSI C compiler". Not really in the FSF spirit, is it?
Also, fixincludes doesn't try to provide an ISO environment, only to fix
things that directly conflict with ISO if they can be fixed without
making things worse.
next prev parent reply other threads:[~1998-07-20 12:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-07-15 11:36 Oliver M. Kellogg
1998-07-15 17:56 ` Richard Henderson
1998-07-16 0:32 ` Jeffrey A Law
1998-07-16 9:26 ` Per Bothner
1998-07-16 22:43 ` Joe Buck
1998-07-16 17:38 ` Per Bothner
1998-07-16 17:47 ` Joe Buck
1998-07-18 13:47 ` Richard Henderson
1998-07-20 12:20 ` Joe Buck [this message]
1998-07-20 12:20 ` Richard Henderson
[not found] ` <199807170027.RAA18575.cygnus.egcs@atrus.synopsys.com>
1998-07-17 16:48 ` Ulrich Drepper
1998-07-16 13:11 ` Richard Henderson
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=199807201609.JAA00421@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=egcs@cygnus.com \
--cc=rth@cygnus.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).