4 ms·
Sure, so some documentation isn't great (and, by having lots of documentation, you might be a bit disappointed at how simple it ends up being). ...but going ba
by maffydub 10y ago
Sure, so some documentation isn't great (and, by having lots of documentation, you might be a bit disappointed at how simple it ends up being).
...but going back to my original point, isn't it more valuable to have a common vocabulary, meaning that I can say "visitor" rather than "pass in a function and descend a graph calling it on each node"?
- emodendroket 10y agoWell, in my opinion, no, because the fancy terminology obscures the simple idea. Also, the naming of the pattern, along with implementation, may push people to copy a design that would be the best way to do it in C++ or Java ca. 2000 but unnatural in whatever they're working in.
- gnaritas 10y agoIt's a simple word, visitor; that's not fancy terminology. Giving things names is not fancy, it's practical and it aids in communicating with other people who do the same thing. You're basically objecting to the fact that people like to give names to their idioms so they communicate better.
- emodendroket 10y agoNo, I'm objecting to the use of terms which I feel make communication worse, rather than better. You're free to disagree.