Re: Mutables Was: [lang] TODO for 2.1

2003-09-02 Thread __matthewHawthorne
prefer keeping all new primitives > > stuff together and focussing [lang] more on Objects. > > > > Stephen > > > > - Original Message - > > From: "Steven Caswell" <[EMAIL PROTECTED]> > > To: "'Jakarta Commons Dev

Re: Mutables Was: [lang] TODO for 2.1

2003-09-02 Thread __matthewHawthorne
Here's an example of the current state: MutableInteger // from Mutable void setValue(Object) Object getValue() // from MutableNumber Number getNumber() void setNumber(Number) // Subclass specific setValue(int) I was assuming that w

Re: Mutables Was: [lang] TODO for 2.1

2003-09-02 Thread Henri Yandell
Mungo Knotwise of Michel Delving > > "One ring to rule them all, one ring to find them..." > > > > > > > -----Original Message- > > > From: __matthewHawthorne [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, September 02, 2003 4:36 PM > > &g

Re: Mutables Was: [lang] TODO for 2.1

2003-09-02 Thread Stephen Colebourne
- From: "Steven Caswell" <[EMAIL PROTECTED]> To: "'Jakarta Commons Developers List'" <[EMAIL PROTECTED]> Sent: Wednesday, September 03, 2003 12:02 AM Subject: RE: Mutables Was: [lang] TODO for 2.1 > I'm still not comfortable with primitive. Yo

RE: Mutables Was: [lang] TODO for 2.1

2003-09-02 Thread Gary Gregory
> From: __matthewHawthorne [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, September 02, 2003 4:36 PM > > To: Jakarta Commons Developers List > > Subject: Re: Mutables Was: [lang] TODO for 2.1 > > > > > > Are we now in agreement about the features for mutable

RE: Mutables Was: [lang] TODO for 2.1

2003-09-02 Thread Steven Caswell
velopers List > Subject: Re: Mutables Was: [lang] TODO for 2.1 > > > Are we now in agreement about the features for mutable > numbers? If so, > I can update my submission with what we've discussed, and > resubmit the > enhancement to [primitives] instead of

Re: Mutables Was: [lang] TODO for 2.1

2003-09-02 Thread Stephen Colebourne
+0.8 ;-) you might want to list the full API for MutableInteger just to be sure...mine below: On Mutable (interface): setValue(Object) getValue() On MutableNumber (interface): getNumber() setNumber(Number) shortNumber() - maybe only on implementation? getShortValue() - synonm for JavaBean tools s

Re: Mutables Was: [lang] TODO for 2.1

2003-09-02 Thread __matthewHawthorne
Are we now in agreement about the features for mutable numbers? If so, I can update my submission with what we've discussed, and resubmit the enhancement to [primitives] instead of [lang]. The primary changes are: - Addition of Mutable interface Mutable setValue(Object) Object getValue(

RE: Mutables Was: [lang] TODO for 2.1

2003-09-02 Thread Steven Caswell
rta Commons Developers List > Cc: [EMAIL PROTECTED] > Subject: Re: Mutables Was: [lang] TODO for 2.1 > > > > > On Mon, 1 Sep 2003, Stephen Colebourne wrote: > > > > > *) Should the MXxxx decorate an Xxxx or an . [ie > primitive or > > >

Re: Mutables Was: [lang] TODO for 2.1

2003-09-01 Thread __matthewHawthorne
> *) Is a .mutable subpackage okay? > > I prefer lang.math > > Boolean? Byte? String? None of these belong in lang.math. You're right... I've never really used bytes, so I wasn't sure where they would fall. I didn't create a mutable boolean since someone suggested otherwise, but if others think