Do we really want extra rules besides what Integer.decode allows? My vote
is to allow anything that Integer.decode can deal with and leave it at
that.... it can deal with hexadecimal, decimal, and octal. If you want
binary, then just figure out the hex or octal for it and use that instead!
:)
FlexInteger? Or does anyone have a better name for it?
Erik
----- Original Message -----
From: "Stefan Bodewig" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, April 15, 2002 3:38 AM
Subject: Re: Number Primitive types
> On Sun, 14 Apr 2002, Peter Donald <[EMAIL PROTECTED]> wrote:
>
> > So basically in the configurer you apply these extra rules ???
>
> Humm, there is a very small possibility of breaking builds with this
> (i.e. people using 010 to mean 10 instead of 8 in their build files).
>
> I'd rather add a new class that performs integer conversions along the
> rules you describe and goes further than Erik's Hex class. Then
> people who want the magic use setters with the new class rather than
> an int/Integer argument.
>
> Stefan
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
