From 87193ca45926a77323b3bddb865bb44fe8663bdd Mon Sep 17 00:00:00 2001 From: Dobiasd Date: Sun, 17 Nov 2013 23:07:17 +0100 Subject: [PATCH] added link to visitor pattern --- from_oop_to_fp_-_inheritance_and_the_expression_problem.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/from_oop_to_fp_-_inheritance_and_the_expression_problem.md b/from_oop_to_fp_-_inheritance_and_the_expression_problem.md index 2f93a2a..2c75f7b 100644 --- a/from_oop_to_fp_-_inheritance_and_the_expression_problem.md +++ b/from_oop_to_fp_-_inheritance_and_the_expression_problem.md @@ -235,7 +235,7 @@ In case `Base.hs` would get too long in our Haskell version we could split in into `Step.hs` and `Display.hs`. But still, if we would like to add a new object, we would have to edit *all* the functions. There would not be one single point to do it. -Vice versa, the OOP solution would make it difficult to add a new +Vice versa, the OOP solution (without [visitor pattern](http://en.wikipedia.org/wiki/Visitor_pattern)) would make it difficult to add a new function. We would have to edit the files of all derived classes. Perhaps this is not a big surprise. In OOP our code is structured by objects,