e most important part, so if
you have one or two classes... then you won't have much connections...).
Peter
On Thu, Jun 08, 2017 at 08:40:34AM +0200, Marc Hanisch via Pharo-users wrote:
> Date: Thu, 8 Jun 2017 08:40:34 +0200
> From: Marc Hanisch
> To: Any question about pharo is welc
--- Begin Message ---
Thanks Todd and Joachim for your fast responses,
your examples are very interesting! I think I got the point! ...And you are
so true about your experience with UML and the struggle to group / align
all graphical objects so it is still understandable ;-)
Best regards,
Marc
2
I think the key to this is intention revealing names and comments. And
shipping unit tests that are the best example of "running documentation".
Take Sven's NeoCSV package as an example. Great documentation and very
good method names. and a complete set of tests.
Sounds frightening at first i
Hi Marc.
In Smalltalk, we rely on naming conventions a lot.
The great thing is that Smalltalk selectors/symbols/method names read like
English.
aDictionary at: aKey put: anObject.
aString indexOf: aCharacter startingAt: start ifAbsent: aBlock
Seems pretty clear, no?
We also rely on comment
--- Begin Message ---
Hello,
I don't know Smalltalk well enough to give myself an answer about the
following topic:
When using design patterns, one benefit of writing interfaces and passing
objects, that implement this interface, to methods is, that the reader
instantly knows: okay, here the meth
