From: Daniel Jacobowitz <drow@mvista.com>
To: Jim Blandy <jimb@zwingli.cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: complex numbers in c-valprint.c
Date: Sun, 03 Feb 2002 14:52:00 -0000 [thread overview]
Message-ID: <20020203175227.A26302@nevyn.them.org> (raw)
In-Reply-To: <npk7tuw5gd.fsf@zwingli.cygnus.com>
On Sun, Feb 03, 2002 at 05:44:50PM -0500, Jim Blandy wrote:
>
> Daniel Jacobowitz <drow@mvista.com> writes:
> > This patch fixes half of gdb/320. The other half is a bug in GCC 3.x, that
> > I just CC'd gdb@ about.
> >
> > Is this OK to commit? Does anyone have a preference for {0, 0} vs. { re =
> > 0, im = 0}? I used the former.
>
> {0, 0} looks to me like GDB's syntax for array literals. In ISO C
> programs, don't you just write complex literals as x+I*y? What's wrong
> with GDB printing that?
>
> If you say, "It shouldn't be an expression!", then I'll just say, "We
> already print negative numbers as an expression!" Lexically speaking,
> C integer literals can't have a sign. `-3' is an application of the
> prefix operator `-' to the literal `3'. Since the spec promises that
> the compiler will fold constant expressions, you don't need a
> dedicated syntax for negative numbers. I assume the same thinking is
> behind the lack of any syntactic support for complex literals.
x + y * I, I think. That's nice; I didn't realize C99 and <complex.h>
supported ``I''.
OK with that syntax change?
> (The bikeshed should be a nice yellow-green, I think.)
...
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-02-03 22:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 20:31 Daniel Jacobowitz
2002-02-03 14:43 ` Jim Blandy
2002-02-03 14:52 ` Daniel Jacobowitz [this message]
2002-02-05 11:24 ` Jim Blandy
2002-02-05 13:41 ` Daniel Jacobowitz
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=20020203175227.A26302@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@zwingli.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