From: Michael Snyder <msnyder@redhat.com>
To: tromey@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: Patch: printing java `char' values
Date: Wed, 08 May 2002 16:52:00 -0000 [thread overview]
Message-ID: <3CD9B721.6207C70@redhat.com> (raw)
In-Reply-To: <87sn52l0at.fsf@creche.redhat.com>
Tom Tromey wrote:
>
> >>>>> "Michael" == Michael Snyder <msnyder@redhat.com> writes:
>
> Michael> I recommend that you emulate what C does, and whenever you
> Michael> have a TYPE_CODE_INT whose length is the length of a char
> Michael> (which for Java appears to be two bytes), you look at the
> Michael> type_name and see if it is "char" -- in which case you print
> Michael> it as a char.
>
> How does this look?
Yes, that's the idea. I wouldn't even bother with the temp variable--
I would just call TYPE_CODE (type) twice. It's a macro, and not
expensive to evaluate. Then you don't need the brackets.
>
> Index: ChangeLog
> from Tom Tromey <tromey@redhat.com>
>
> * jv-valprint.c (java_val_print): Handle `char' as a special case
> of TYPE_CODE_INT.
>
> Index: jv-valprint.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/jv-valprint.c,v
> retrieving revision 1.9
> diff -u -r1.9 jv-valprint.c
> --- jv-valprint.c 21 Oct 2001 01:57:42 -0000 1.9
> +++ jv-valprint.c 8 May 2002 22:41:22 -0000
> @@ -497,20 +499,21 @@
> return i;
>
> case TYPE_CODE_CHAR:
> - format = format ? format : output_format;
> - if (format)
> - print_scalar_formatted (valaddr, type, format, 0, stream);
> - else
> - LA_PRINT_CHAR ((int) unpack_long (type, valaddr), stream);
> - break;
> -
> case TYPE_CODE_INT:
> /* Can't just call c_val_print because that print bytes as C chars. */
> format = format ? format : output_format;
> if (format)
> print_scalar_formatted (valaddr, type, format, 0, stream);
> else
> - val_print_type_code_int (type, valaddr, stream);
> + {
> + enum type_code code = TYPE_CODE (type);
> + if (code == TYPE_CODE_CHAR
> + || (code == TYPE_CODE_INT && TYPE_LENGTH (type) == 2
> + && ! strcmp (TYPE_NAME (type), "char")))
> + LA_PRINT_CHAR ((int) unpack_long (type, valaddr), stream);
> + else
> + val_print_type_code_int (type, valaddr, stream);
> + }
> break;
>
> case TYPE_CODE_STRUCT:
next prev parent reply other threads:[~2002-05-08 23:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-06 10:11 Tom Tromey
2002-05-06 17:05 ` Michael Snyder
2002-05-07 13:29 ` Tom Tromey
2002-05-07 15:45 ` Andrew Cagney
2002-05-07 13:43 ` Daniel Jacobowitz
2002-05-07 14:22 ` Michael Snyder
2002-05-07 14:35 ` Tom Tromey
2002-05-08 12:12 ` Michael Snyder
2002-05-08 12:47 ` Daniel Jacobowitz
2002-05-08 13:32 ` Tom Tromey
2002-05-08 13:46 ` Daniel Jacobowitz
2002-05-08 14:10 ` Michael Snyder
2002-05-08 14:20 ` Daniel Jacobowitz
2002-05-08 15:39 ` Michael Snyder
2002-05-08 15:42 ` Tom Tromey
2002-05-08 16:52 ` Michael Snyder [this message]
2002-05-08 21:09 ` Tom Tromey
2002-05-09 11:09 ` Michael Snyder
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=3CD9B721.6207C70@redhat.com \
--to=msnyder@redhat.com \
--cc=gdb-patches@sources.redhat.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