1) write them by hand
annoying typing required
2) use Class refactorings (right click on class -> refactoring -> class refactoring -> generate accessors; or ctrl+h+a)
this will ask you to choose for all attributes… good initially, but really stupid if you are providing e.g. just getters (because then you would need to cancel genreation for all the attributes)
3) use attribute refactorings (right click on class -> refactoring -> inst var refactoring -> accessors -> select attribute)
good for individual attributes
4) write the code compilation (ideally as part of some tool)
MyClass compile: 'attr ^ attr' classified: 'accessing'.
MyClass compile: 'attr: anObject attr := anObject' classified: 'accessing'.
Much more typing, but good if you have it as part of some tool (so you can quickly script a gui that would generate it just by clicking on a checkbox or something)
5) use refactoring (this is what the System Browser uses internally)
(RBCreateAccessorsForVariableRefactoring
variable: #attr class: MyClass classVariable: false) execute
6) use TDD (test driven development)
the Debugger will offer you to create the method and you can modify it as you work through (I don't know if TDD is already part of the broadcasted MOOC courses)
Typing by hand is annoying, but it's literally two words for getter and four for setter.
This mail is probably more words than all the accessors I've created this year… so typing it by hand is no big deal.
More importantly the autogenerated code is a bit stupid
TBPost >> title: anObject
title := anObject
this is stupid, so even for generated one I select the argument, press ctrl+t (or right click + suggestions) and select 'rename' ... and rename it into something meaningful like
TBPost >> title: aString
title := aString
But otherwise I regularly use all 1, 2, 4, 5, 6…
I never use 3) it's too annoying and distracting because I have to read the labels… I can type in the getter/setter without breaking focus on what I am doing… but it just gave me an idea... :)
Peter
Locked
