Hi!

I'm really sorry for the late reply. I'm not very familiar with Dart, but it's very likely that you'll be able to follow the course just fine. It doesn't require any specific knowledge of Java, C# or PHP. The OOP principles and refactoring techniques covered in the course should be applicable to any modern OOP language.

Hi! No, sorry, not yet.

Hi Eric!

As far as I know, C is not an OOP language, therefore the patterns aren't applicable there. Probably there are design patterns specific to the C language, but since they are very specialized, I doubt that they'll be covered here.

Muito obrigado!

Btw, using an iterator along with the visitor is a very common thing.

From what I see, you'll have to depend on some of the concrete classes from the original tree anyway, unless it exposed methods to distinguish between leaf/component classes. So, the question seems to be where that dependency is least awkward to have. If you're building a universal mapper, certainly you should provide some means to inject that dependency to the mapper. But if it's a mapper built for a specific thing, which unlikely to be changed in the near future, I'd always go the easy route and hardcode the required tree classes in it. You can always refactor your way out of it if needed.

Fixed, thanks!

Hi Anne!

Thanks for asking! When people ask me questions regarding their own projects & code, the first counter-question I ask is: what do you think is the answer? Sometimes people don't realize they have perfectly good answers for their own questions.

I mean why do you NEED to use a pattern at all? Implement the code without a pattern and then see whether applying a pattern would improve your code. This is the approach I usually take in real-life coding.