From: James E Wilson <wilson@specifix.com>
To: "Rafael Ávila de Espíndola" <rafael.espindola@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: can DECL_RESULT be 0?
Date: Mon, 21 Nov 2005 21:19:00 -0000 [thread overview]
Message-ID: <1132607938.11623.17.camel@aretha.corp.specifix.com> (raw)
In-Reply-To: <200511201801.59206.rafael.espindola@gmail.com>
On Sun, 2005-11-20 at 12:01, Rafael Ãvila de EspÃndola wrote:
> What do you thing about adding an assert? Something similar to the attached
> patch.
I think there is no chance of a user seeing this problem. It can only
occur when working on a front end, in which case the problem would be
obvious to the developer, and would be fixed before end users ever saw
it. I don't really see a need for extra checks here.
--
Jim Wilson, GNU Tools Support, http://www.specifix.com
prev parent reply other threads:[~2005-11-21 21:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-12 12:03 Rafael Ávila de Espíndola
2005-11-15 0:33 ` Jim Wilson
2005-11-15 2:17 ` Gabriel Dos Reis
2005-11-15 2:40 ` James E Wilson
2005-11-15 21:30 ` Rafael Ávila de Espíndola
2005-11-18 1:35 ` Jim Wilson
2005-11-20 19:58 ` Rafael Ávila de Espíndola
2005-11-21 21:19 ` James E Wilson [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=1132607938.11623.17.camel@aretha.corp.specifix.com \
--to=wilson@specifix.com \
--cc=gcc@gcc.gnu.org \
--cc=rafael.espindola@gmail.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).