Other Design Patterns (OOP and non OOP)

[Lauke]

Hi Guys,

I was looking for other design pattern in literature. I mean the most famous ones are the 15 Patterns of the GoF, but i was curious if there's any other OO design pattern.

Moreover is there any design pattern suitable for non OOP programming (for C programming of course).

Again... i was interested in variant of the Observer design pattern.

Thank you

[Lachlan Easton]

http://gameprogrammingpatterns.com/ covers a number of interesting programming patterns. They are aimed at being helpful for video games but can still be useful information in other fields.
You may also want to look up functional programming(http://en.wikipedia.org/wiki/Functional_programming ) which is more or less the antithesis of OOP, which is by no means a bad thing, they are both very valid and useful paradigms.
Edit: fixed FP link

[Lauke]

Yes but... is there some other books? or something of free in general?

Anyway i'm not an expert, but i have to design a sort of general optimization module (an object of a given class) which depends on the iteration of other two object belonging to other two classes. So what i have is these three object but i don't want they are too coupled.

So i was thinking to implement an observer pattern, but i'm not too sure because maybe this pattern needs to be implemented by a multithreading programming, and potentially i would avoid it.

Any suggestion?

[Duthomhas]

I wouldn't call FP the antithesis of OOP. They are functionally equivalent.

[Lachlan Easton]

Not if you're programming in Java (tongue in cheek) http://steve-yegge.blogspot.com.au/2006/03/execution-in-kingdom-of-nouns.html

Ontopic: The book I posted has a chapter on the observer pattern http://gameprogrammingpatterns.com/observer.html
The pattern itself doesn't require threading (unless I'm mistaken)

[Lauke]

What about multithreading design pattern instead?
To be honest i have some difficult to find some specialized literature.

My reference is GoF but they speaks about the pattern in general, very useful but i think i have to spent time in understanding ho to apply them in a particular problem.

I think i'm able to recognize where to apply a pattern, to problem is the implementation itself.
For example i'm pretty sure that for my problem, abstractly speaking, the observer pattern will be pretty useful. But i have to specialize some interaction, the update should present some little difference respect to the normal pattern.