From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: msnyder@sonic.net, gdb-patches@sourceware.org, gaius@glam.ac.uk
Subject: Re: [RFC] logic change in m2-valprint.c
Date: Tue, 03 Jul 2007 07:42:00 -0000 [thread overview]
Message-ID: <200707030741.l637fhwb007184@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <20070703011147.GA26350@caradoc.them.org> (message from Daniel Jacobowitz on Mon, 2 Jul 2007 21:11:47 -0400)
> Date: Mon, 2 Jul 2007 21:11:47 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> On Mon, Jul 02, 2007 at 05:05:12PM -0700, Michael Snyder wrote:
> > is nowhere else for it to be set false), and there is no second
> > time -- we will never enter this block again because we will set
> > "element_seen" to true (and there is nowhere else for it to be
> > set false again).
> >
> > Was that clear?
>
> Clear, but not right.
>
> 152 element_seen = 0;
>
> On entry, empty_set = 1 and element_seen = 0. We see an element,
> which causes us set empty_set = 0 and element_seen = 1. Then we see a
> clear bit in the set and set element_seen to 0 and not change
> empty_set. Then we see a set bit, and element_seen == 0 with
> empty_set == 0. We print the comma.
>
> I would test it, but I don't have an M-2 compiler and the expression
> parser can't create sets. Am I missing something?
Dunno, but it is obvious that this bit of code is in need of a rewrite.
next prev parent reply other threads:[~2007-07-03 7:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-29 0:37 msnyder
2007-07-01 15:49 ` Daniel Jacobowitz
2007-07-01 15:54 ` Michael Snyder
2007-07-01 16:03 ` Daniel Jacobowitz
2007-07-03 0:05 ` msnyder
2007-07-03 1:12 ` Daniel Jacobowitz
2007-07-03 1:21 ` msnyder
2007-07-03 1:24 ` Daniel Jacobowitz
2007-07-03 1:40 ` msnyder
2007-07-03 7:42 ` Mark Kettenis [this message]
2007-07-03 19:26 ` Jim Blandy
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=200707030741.l637fhwb007184@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=drow@false.org \
--cc=gaius@glam.ac.uk \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@sonic.net \
/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