From: Daniel Jacobowitz <drow@mvista.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sources.redhat.com, per@bothner.com
Subject: Re: Fix PR gdb/265, 64-bit pointers in Java
Date: Mon, 11 Feb 2002 10:31:00 -0000 [thread overview]
Message-ID: <20020211133148.A16621@nevyn.them.org> (raw)
In-Reply-To: <87k7tjj1on.fsf@creche.redhat.com>
On Mon, Feb 11, 2002 at 11:47:20AM -0700, Tom Tromey wrote:
> >>>>> "Daniel" == Daniel Jacobowitz <drow@mvista.com> writes:
>
> Daniel> I don't know if Java allows the implicit 0x123456789 ->
> Daniel> 0x123456789L conversion that we all know and love in C
>
> Nope. In Java an integer constant which is too big for its type is an
> error.
>
> Daniel> but it certainly behooves us to act that way on the command
> Daniel> line.
>
> If/when we implement method invocation, won't this mean we could
> silently call the wrong overloaded method?
Only if the user specifies a constant too large. Normal constants are
still maintained as java_int_type. But if that becomes an issue we can
add a flag to parse_number later to conditionalize this, and modify the
parser appropriately. x/i (for instance) should always accept 64-bit
constants.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-02-11 18:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-10 21:38 Daniel Jacobowitz
2002-02-11 10:24 ` Tom Tromey
2002-02-11 10:31 ` Daniel Jacobowitz [this message]
2002-02-20 14:41 ` Daniel Jacobowitz
2002-02-20 15:04 ` Per Bothner
2002-02-20 15:44 ` Daniel Jacobowitz
2002-02-20 17:30 ` Per Bothner
2002-02-20 18:05 ` Daniel Jacobowitz
2002-02-20 18:11 ` Per Bothner
2002-02-20 18:55 ` 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=20020211133148.A16621@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=per@bothner.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