+1 depricate the oldOn 4/21/06, Juergen Donnerstag [EMAIL PROTECTED] wrote:
+1On 4/21/06, Martijn Dashorst [EMAIL PROTECTED]
wrote: +1 On 4/21/06, Vincent Jenks [EMAIL PROTECTED] wrote: +1 - it's certainly easier on the eyes.
On 4/21/06, Igor Vaynberg [EMAIL PROTECTED] wrote: +1 we can
doneOn 4/22/06, Johan Compagner [EMAIL PROTECTED] wrote:
+1 depricate the oldOn 4/21/06, Juergen Donnerstag
[EMAIL PROTECTED] wrote:
+1On 4/21/06, Martijn Dashorst
[EMAIL PROTECTED]
wrote: +1 On 4/21/06, Vincent Jenks [EMAIL PROTECTED]
wrote: +1 - it's certainly easier on the eyes.
On
I'm not sure setReuseItems is the best name, but I not a friend of
setUseOptimizedItemRemoval.
Eelco
On 4/21/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
+1
we can deprecate the existing one and have it forward to the new one as not
to break the api. then remove the deprecated method once 1.2
I vote in favor of renaming setUseOptimizedItemRemoval() to
setReuseItems() because I feel it is more descriptive of what it
actually does. What do the rest of you think?
Thanks,
Gili
signature.asc
Description: OpenPGP digital signature
+1we can deprecate the existing one and have it forward to the new one as not to break the api. then remove the deprecated method once 1.2 is out of the door.-Igor
On 4/21/06, cowwoc [EMAIL PROTECTED] wrote:
I vote in favor of renaming setUseOptimizedItemRemoval() tosetReuseItems() because I feel
+1On 4/21/06, Vincent Jenks [EMAIL PROTECTED] wrote:
+1 - it's certainly easier on the eyes.On 4/21/06, Igor Vaynberg [EMAIL PROTECTED] wrote: +1 we can deprecate the existing one and have it forward to the new one as not
to break the api. then remove the deprecated method once 1.2 is out of the
