That's excellent :) I'm very much for removing API clutter.
On a related note (cleaning up the API etc), would it be possible to
rename ExpressionFactory.fooExp() to ExpressionFactory.foo()? Purely
from a readability point of view, I prefer
ExpressionFactory.greaterThan() to ExpressionFactory.greaterThanExp()
Gili
Andrus Adamchik wrote:
> Yeah, you are right on all counts. It was deprecated to keep API lean.
> And it is already gone from 1.2.
>
> Andrus
>
>
> On Sep 5, 2005, at 3:38 PM, Cris Daniluk wrote:
>
>> I think it was claimed that the stuff deprecated in 1.1 will be gone
>> in 1.2. I don't think its happened yet though. Andrus could clarify :)
>>
>>
>> On 9/5/05, Gili <cowwo..bs.darktech.org> wrote:
>>
>>>
>>> Ok, sounds good. I guess this means we remove deprecated
>>> methods after
>>> X releases?
>>>
>>> Thank you,
>>> Gili
>>>
>>> Cris Daniluk wrote:
>>>
>>>> Use DataContext.invalidateObjects(Collection.singletonList (object))
>>>> instead.
>>>>
>>>> The object method was deprecated because its often necessary to
>>>> deprecate (or delete or... or...) a collection of objects. Rather than
>>>> cluttering the API with 2 methods for each case of this, its cleaner
>>>> to just have 1...
>>>>
>>>> On 9/3/05, Gili <cowwo..bs.darktech.org> wrote:
>>>>
>>>>
>>>>> Hi,
>>>>>
>>>>> Just wondering why this method is deprecated. It seems
>>>>> useful enough as
>>>>> a convenience method...
>>>>>
>>>>> Gili
>>>>> --
>>>>> http://www.desktopbeautifier.com/
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>> --
>>> http://www.desktopbeautifier.com/
>>>
>>>
>>
>>
>
>
-- http://www.desktopbeautifier.com/
This archive was generated by hypermail 2.0.0 : Mon Sep 05 2005 - 15:47:42 EDT