[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] Generics and APIs
|
I strongly disagree, on both points. Avoiding 1.5 language features
will hold back our productivity and limit the quality and
maintainability of new code. To turn off generics warnings
effectively does away with the benefits of using generics. Generics
don't affect generated code, but they allow a developer to write code
that is guaranteed to be type safe...as long as he ensures he has no
warnings. Ignore the warnings and you might as well not use generics.
John
At 03:05 PM 4/10/2008, Elena Laskavaia wrote:
Personally I think we should avoid java 1.5 all together, and I don't
think we should change API just to remove warnings. I think these
particular warnings should be turned off.
Jason Montojo wrote:
>
> Hi everyone,
>
> I've been fixing compiler warnings about generics in the language mapping
> classes. This involved having to change a number of method signatures to
> account for parameterized collections. For example, I changed this in
> LanguageManager:
>
> Old:
> public Map getContentTypeIdToLanguageDescriptionsMap(){ ... }
>
> New:
> public Map<String, ILanguageDescriptor[]>
> getContentTypeIdToLanguageDescriptionsMap(){ ... }
>
> Such a change wouldn't break existing clients and it makes the API much
> easier to work with. Regardless, it is still an API change.
>
> Should I go ahead and make the changes to the signatures? Or should I
> leave them as-is? I know we're already past the API freeze so I'd
> like to
> know how the community feels about this.
>
> Thanks,
> Jason Montojo
> IBM CDT Team
> IBM Toronto Lab
> 905-413-5228
> jmontojo@xxxxxxxxxx
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
