Exceptions and the Liskov Substitution Principle

Consider the following scenario.

Are there any situations in which you might consider “stacking” Python decorators/decorator implementations more than 2 layers deep?

As many of you probably know, you can use decorators (sometimes called annotations, in eg Java) to do automagic registration of objects into easily usable data structures, like lists or dictionaries, in such a way that you don’t have to update these “meta” data strucutres; any new code you decorate gets into it automatically.

What are the benefits of using a ‘decorator factory’ that decorates objects?

In a project I decided to implement the Decorator pattern.

Decorator Pattern: can it solve issues arising from changes to underlying code?

I understand that decorators solve the problem of needing to mix and match behaviors, but it was suggested that I could use the decorator pattern to solve issues of brittleness that might arise due to changes in the underlying base code.

Decorator Pattern: can it solve issues arising from changes to underlying code?

I understand that decorators solve the problem of needing to mix and match behaviors, but it was suggested that I could use the decorator pattern to solve issues of brittleness that might arise due to changes in the underlying base code.

Decorator Pattern: can it solve issues arising from changes to underlying code?

I understand that decorators solve the problem of needing to mix and match behaviors, but it was suggested that I could use the decorator pattern to solve issues of brittleness that might arise due to changes in the underlying base code.

Pattern for caching DAOs: strategy or decorator?

I’m building a php system with the Services/DAOs/Domain Models pattern, and now is the time to implement a caching system for the DAOs.

Unsure about the decorator design pattern

I’m fairly new at using design patterns and I am currently making a small game for my uni course that I have to use the decorator pattern for creating the different classes of NPC however I think that I have misunderstood how the decorator pattern works.

Is it possible to save and load a decorated object

I am wondering if there is an easy way to save and load a decorated object in c++ as i have never done file handling in C++ before.

Design pattern where decorated object may ask for things like “status updates” from the decorator to perform it’s role?

Here’s an situation that has haunted one of my open-source projects for quite some time.