Bridging pattern

http://wiki.c2.com/?BridgePattern

https://web.archive.org/web/20160317135644/http://delphipatterns.blog.com/2011/02/22/bridge/

https://web.archive.org/web/20110604051641/http://home.earthlink.net/~huston2/dp/bridge.html "....The Bridge pattern decouples an abstraction from its implementation, so that the two can vary independently. A household switch controlling lights, ceiling fans, etc. is an example of the Bridge. The purpose of the switch is to turn a device on or off. The actual switch can be implemented as a pull chain, simple two position switch, or a variety of dimmer switches. [Michael Duell, "Non-software examples of software design patterns", Object Magazine, Jul 97, p54]...."

What this Category mistake means in English is to view everything in oop and "functional" programming a function which takes a pointer to another function as a parameter in c coding and how you represent this with morphisms in Category theory, the branch of math OOP math frauds actually use as they laugh at everyone trying to figure out their cypher language of factory patterns getting visitor patterned before getting Haskell monaded.

https://web.archive.org/web/20071026035244/http://wiki.cs.uiuc.edu/PatternStories/BridgePattern

links
Design patterns

Oop in c the trick to grasping design patterns is to sketch its out in plain in c where the functions take a pointer to a function as a parameter. The fact that you don't know this, is because your "software engineer" maths professor want's to get rid of you.