public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: Steven Bosscher <stevenb.gcc@gmail.com>
Cc: Tom Tromey <tromey@redhat.com>, GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: Remove "asssertions" support from libcpp
Date: Fri, 13 Aug 2010 08:14:00 -0000	[thread overview]
Message-ID: <mcrhbizb153.fsf@google.com> (raw)
In-Reply-To: <AANLkTimhffLNTjBoFQEfLNS0+Bpqr6w4S2ihiXDgMDpY@mail.gmail.com>	(Steven Bosscher's message of "Tue, 10 Aug 2010 07:57:35 +0200")

Steven Bosscher <stevenb.gcc@gmail.com> writes:

> Assertions in libcpp have been deprecated since r135264:
>
> 2008-05-13  Tom Tromey  <tromey a redhat dot com>
>
>         PR preprocessor/22168:
>         * expr.c (eval_token): Warn for use of assertions.
>
> Can this feature be removed for GCC 4.6?

It was officially deprecated in the 4.4 release notes, so I think it can
be removed in 4.6.

Ian

      parent reply	other threads:[~2010-08-13  4:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-10 15:53 Steven Bosscher
2010-08-10 23:39 ` Tom Tromey
2010-08-13  8:14 ` Ian Lance Taylor [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=mcrhbizb153.fsf@google.com \
    --to=iant@google.com \
    --cc=gcc@gcc.gnu.org \
    --cc=stevenb.gcc@gmail.com \
    --cc=tromey@redhat.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).