Thanks a lot for your suggestion. I will work on that.
I'd say that a good question would be "how you can add
functionality without changing the code"? I think it's a win. The
ability to do that means that you are not introducing bugs on
existing code, you don't have maintenance costs associated to code
which already works well. This sort of benefit does not apply
always and everywhere, but when applies, it is a win!
But there's no free lunch in life: there's always a price to be
paid... and it is complexity in this case.
Things are complex until you understand them, or until you
reorganize concepts inside your head and document them.
If you have people willing to read the documentation and explore
what it evolves, they will ultimately understand what is going on,
So, I think that things remain complex/obscure only to people not
willing to invest time/effort on them, for whatever reasons they
have, which I definitely respect, by the way.
On 31/01/13 10:49, Abraham Marín Pérez wrote:
I like the idea of having a good explanation about the
visitor pattern, because I must admit when I first heard
about how to separate data structure from algorithm my
reaction was "isn't that exactly the opposite of what we
intend to do with OOP?"
If you'd like to split I'd suggest two articles: the
first one presenting the problem, ie the situation in which
you need to separate data and code, and the second
explaining the pattern as a solution.
On 30 Jan 2013, at 20:41, Richard Gomes <[address removed]>
This message exceeded the Maximum Message Size
set in Account Settings, so we have only
downloaded the first few lines from the mail
the rest of the message.