From: Jeffrey A Law <law@hurl.cygnus.com>
To: Gavin Romig-Koch <gavin@cygnus.com>
Cc: egcs@cygnus.com
Subject: Re: strict_prototypes_lang_c
Date: Tue, 15 Dec 1998 09:57:00 -0000 [thread overview]
Message-ID: <24002.913744542@hurl.cygnus.com> (raw)
In-Reply-To: <13942.31893.760353.315840@cetus.cygnus.com>
In message < 13942.31893.760353.315840@cetus.cygnus.com >you write:
> > Personally, I agree.
>
> >From this thread it sounded like the primary reason for turning
> on -trigraphs is to make "what's on by default" be a superset of
> ANSI/ISO because that would make the options simpler. If I
> understood this correctly, I think it's a mistake.
I can't speak for Mark, but for myself, it's merely a standards conformance
issue. When in doubt I'll err on the side of following a standard instead of
doing something non-standard.
jeff
next prev parent reply other threads:[~1998-12-15 9:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-13 17:10 strict_prototypes_lang_c Mark Mitchell
1998-12-14 16:04 ` strict_prototypes_lang_c Martin von Loewis
1998-12-14 22:51 ` strict_prototypes_lang_c Jeffrey A Law
1998-12-15 0:00 ` strict_prototypes_lang_c Mark Mitchell
1998-12-15 0:36 ` strict_prototypes_lang_c Jeffrey A Law
1998-12-15 7:16 ` strict_prototypes_lang_c Gavin Romig-Koch
1998-12-15 9:23 ` strict_prototypes_lang_c Mark Mitchell
1998-12-15 9:57 ` Jeffrey A Law [this message]
1998-12-15 10:51 ` strict_prototypes_lang_c Joe Buck
1998-12-15 22:51 ` strict_prototypes_lang_c Jeffrey A Law
1998-12-16 22:49 ` strict_prototypes_lang_c Joern Rennecke
1998-12-15 14:36 ` strict_prototypes_lang_c Martin von Loewis
1998-12-15 15:12 ` strict_prototypes_lang_c Per Bothner
1998-12-15 9:38 ` strict_prototypes_lang_c Joe Buck
1998-12-15 9:55 ` strict_prototypes_lang_c Jeffrey A Law
1998-12-16 2:49 ` strict_prototypes_lang_c Richard Earnshaw
1998-12-15 5:34 ` strict_prototypes_lang_c Horst von Brand
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=24002.913744542@hurl.cygnus.com \
--to=law@hurl.cygnus.com \
--cc=egcs@cygnus.com \
--cc=gavin@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).