5 ms·
This... I can actually see the point in this. The Visitor pattern is one of those patterns I never really saw the point of, and which mostly struck me as an ove
by mcv 8y ago
This... I can actually see the point in this. The Visitor pattern is one of those patterns I never really saw the point of, and which mostly struck me as an over-engineered hack about a shortcoming in a language.
This example actually makes clear why you'd need to do it this was in C++ at least. Not sure which other languages would need this. It's certainly not pretty. Then again, dispatching twice is not so bad compared to your average Java-style over-engineering.
- yvdriess 8y agoI've always heard that pattern itself is older than C++, originating from Smalltalk.
- scroot 8y agoIt does come from Smalltalk, which is in part why it looks so sloppy and strange in other languages (a Ruby example I saw even had an intermediary class for the visitor part, which doesn't really happen in Smalltalk). The reason to use this pattern is to leverage real polymorphism. In Squeak/Pharo, the graphics system is called Morphic, which uses this pattern all the time to draw different kinds of objects to different kinds of Canvases. With a visitor pattern, each object can "know" how to draw itself to a given canvas.
- moron4hire 8y agoIt's not a "shortcoming" of the language per se. Visitor is a mitigation of the Expression Problem[0] on the Object Oriented spectrum. Object oriented designs need to use Visitor to add functionality to existing data structures, whereas doing such is a natural feature of Functional languages (though FP languages have their own awkward angle in attempting to add new data structures to existing functionality). This is a big motivator for most modern programming languages supporting multiple design paradigms. [0] https://eli.thegreenplace.net/2016/the-expression-problem-and-its-solutions/ https://eli.thegreenplace.net/2016/the-expression-problem-an...
- barrkel 8y agoIt's a shortcoming of languages that don't have multiple dispatch.
- geezerjay 8y agoWhy should anyone force changes into the core language if all you want to do is use an obscure programming construct in a corner case that's easily implemented with a design pattern? Some of these complains are at best very misguided.
- bstamour 8y agoWhy have functions and control structures when we can just jmp?
- geezerjay 8y agoThat's a disingenuous comparison. Functions are used pervasively, but even the visitor pattern isn't used very often.
- bstamour 8y agoBut in languages that support multiple dispatch at the language level, they're just another way of writing polymorphic functions. They're not just a niche feature. When you don't have to write all of the ceremony of the visitor pattern, it's easier to use visitors everywhere without thinking about them.
- kazinator 8y agoThe short answer is that the existence of multiple dispatch isn't motivated by the visitor pattern. Moreover, multiple dispatch isn't obscure at all. C++ has it, but only statically, for instance, in the form of overloaded functions. C++ chooses a function overload by looking at the types of all parameters and arguments. Multiple dispatch is similar, but the run-time types of the arguments are used. This is broadly applicable in making all sorts of situations nicer.
- cjhanks 8y agoA state machine with context is one case I have used it for.