From: Richard Stallman <rms@gnu.org>
Cc: dann@ics.uci.edu, emacs-devel@gnu.org
Subject: Re: Problem report #
Date: Mon, 01 May 2006 00:20:18 -0400 [thread overview]
Message-ID: <E1FaPtS-00047i-KP@fencepost.gnu.org> (raw)
In-Reply-To: <20060430175859.GA6489@rocksteady.printf.se> (message from Henrik Enberg on Sun, 30 Apr 2006 19:58:59 +0200)
> Event const: After this line, the value of "type_seen" is equal to 1
> Event assignment: Assigning "1" to "type_seen"
> Also see events: [dead_error_line][dead_error_condition][assignment]
Uhm, as far as I can tell, type_seen may very well be 0 after this.
There are several cases where the code won't goto the typeseen label.
I agree. I think the report is a confusion.
Dan, please mark this as not a real bug.
prev parent reply other threads:[~2006-05-01 4:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-30 16:40 Problem report # Dan Nicolaescu
2006-04-30 17:58 ` Henrik Enberg
2006-05-01 4:20 ` Richard Stallman [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1FaPtS-00047i-KP@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).