|
|
|
Re: How to turn off 'final' completion in 3.7 [message #665035 is a reply to message #665033] |
Wed, 13 April 2011 01:53 |
Deepak Azad Messages: 543 Registered: July 2009 |
Senior Member |
|
|
On 4/13/2011 6:16 AM, Miles Parker wrote:
> Deepak Azad wrote on Tue, 12 April 2011 20:36
>> I think you have enabled 'Use final where possible' cleanup (the
>> cleanup is not new in Indigo).
>>
>> Preferences > Java > Code Style > Clean Up --> Edit --> Code style tab
>
>
> Hi Deepak,
>
> Thanks for the idea. I just checked and that is not enabled. I also get
> the same thing happening with the default Eclipse clean profile. Just as
> a sanity check, what happens for you in Indigo when you use proposals?
> For example:
>
> a) Add a parameter to a constructor
> b) Choose the "Assign Parameter to new Field" proposal.
>
> I end up with:
>
> private final boolean something;
>
> Whereas previously I'd get:
>
> private boolean something;
>
> thanks,
>
> Miles
>
Ok, I see it now. "Assign Parameter to new Field" when invoked from a
constructor does insert a final, but not when invoked from a method.
However this is not new in 3.7, it works the same way in 3.6 as well.
Miles, you can open a bug with JDT/UI if you want something done here..
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02537 seconds