Additionally it was annoying if a superclass has a method with the same name. 
For example if you have a name var and you create accessors I’d like to have 
actually a ’name’ getter and not ’name1’

Uko

> On 6 Dec 2016, at 11:16, Nicolai Hess <[email protected]> wrote:
> 
> 
> 
> 2016-12-06 11:09 GMT+01:00 Denis Kudriashov <[email protected] 
> <mailto:[email protected]>>:
> Hi.
> 
> There is very annoying logic of accessors refactoring. 
> For example imaging your class already has getter for variable #myInstVar but 
> with some extra code instead of simple return. For example it could be lazy 
> initialization:
> 
> MyClass>>myInstVar
>    ^myInstVar ifNil: [#someValue]
> 
> In that case accessors generator will suggest you new getter method 
> #myInstVar1. 
> I really doubt that anybody accept generation of such method. 
> I always remove it from changes list which is very annoying.
> 
> Am I alone about it? Can we remove this logic?
> 
> Best regards,
> Denis
> 
> 18880 
> <https://pharo.fogbugz.com/f/cases/18880/Autogenerating-accessors-should-be-less-naive>
>  Autogenerating accessors should be less naive

Reply via email to