Hi!

Please, take a look at this answer: https://feedback.refactoring.guru/helpdesks/2/tickets/702-missing-interpreter-pattern-in-behavioral-section#comment-940

The Ruby examples are indeed planned, but at this point, the earliest date I envision them to be implemented is the beginning of 2019.

If someone is willing to help me with this, please shoot me an email to support@refactoring.guru

Thanks, Murilo! We're going to have a huge update for the design patterns section in September. Until then, I apologize for a huge number of errors and imperfections you might encounter in that section at the moment.

Thanks, Pratik!

Thanks, Lucas!

Thanks, Jacek!

Hi Muhammed!

This sounds really cool, but I'm not sure whether I'll be able to implement something like that.

Hi!

Thanks! I'm glad that my content is helpful to you! I didn't describe the Interpreter pattern simple because it is very rare and quire complex. As a software developer with 20 years of experience you could have used all 22 patterns but that one. I like to share this link when answering the questions about Interpreter: http://blogs.perl.org/users/jeffrey_kegler/2013/03/the-interpreter-design-pattern.html

There is a big irony in fact that I had used the Interpreter pattern to build the engine for live examples, which are part of the Refactoring Course. A live example looks pretty much as a short video which shows the sequence of refactoring steps. The actions that take place in a live examples in fact are being interpreted from a scenario like this one: https://raw.githubusercontent.com/RefactoringGuru/refactoring-examples/master/interactive/java/add-parameter.md