This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Fix PR gdb/265, 64-bit pointers in Java


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]