On 2010-04-07, at 1:32 PM, Mike Schrag wrote:
> 3.6 cocoa is better, but still has performance problems. I'm still debating about what my plan will be here. Personally, I don't turn off that warning because it punishes you for doing potentially bad things.
Yes, that kind of sums up my view. In general, I try and eliminate the warnings by fixing the code, but sometimes that is not practical. Adding a..uppressWarning is grating enough to not be something I do lightly.
>
> ms
>
> On Apr 7, 2010, at 1:28 PM, Marius Soutier wrote:
>
>> Why not disable the warning altogether in your Eclipse preferences? IMHO the..uppressWarnings annotation is noise anyway.
>>
>> Is the 3.6 Cocoa build usable (as in "responsive")?
>>
>>
>> - Marius
>>
>> On 07.04.2010, at 18:05, David LeBer wrote:
>>
>>>
>>> I'm testing Eclipse 3.6 and the behaviour of..uppressWarnings "unchecked" token has changed. It was arguably too broad in 3.5 and earlier. In 3.6 it's behaviour has been broken into "unchecked" and "rawtypes".
>>>
>>> This is not a big deal, but it makes it difficult to have warnings free code if you have team members working on 3.6 and earlier versions of Eclipse.
>>>
>>> Discussion: <https://bugs.eclipse.org/bugs/show_bug.cgi?id=290034>
>>>
>>> ;david
>>>
>>> --
>>> David LeBer
>>> Codeferous Software
>>> 'co-def-er-ous' adj. Literally 'code-bearing'
>>> site: http://codeferous.com
>>> blog: http://davidleber.net
>>> profile: http://www.linkedin.com/in/davidleber
>>> twitter: http://twitter.com/rebeld
>>> --
>>> Toronto Area Cocoa / WebObjects developers group:
>>> http://tacow.org
>>>
>>>
>>
>>
>
>
;david
-- David LeBer Codeferous Software 'co-def-er-ous' adj. Literally 'code-bearing' site: http://codeferous.com blog: http://davidleber.net profile: http://www.linkedin.com/in/davidleber twitter: http://twitter.com/rebeld -- Toronto Area Cocoa / WebObjects developers group: http://tacow.org
This archive was generated by hypermail 2.0.0 : Wed Apr 07 2010 - 13:44:14 EDT