Programming Paradigms
Quote:Contrasted paradigms: * Structured programming vs. Unstructured programming * Imperative programming vs. Declarative programming * Procedural programming vs. Functional programming * Value-level programming vs. Function-level programming * Flow-driven programming vs. Event-driven programming * Scalar programming vs. Array programming * Within Object-oriented programming: Class-based programming vs. Prototype-based programming * Within Logical programming: Rule-based programming vs. Constraint programmingNon-contrasted paradigms: * Component-oriented programming à la OLE * Aspect-oriented programming à la AspectJ * Relational programming à la SQL * Symbolic programming à la Stephen Wolfram's MathematicaCandidate paradigms: * Post-object programming * Subject-oriented programming * Intentional programming * Reflective programming
See WiKi for more information [smile]
Regards,
Pat.
I prefer Component-Oriented programming over the other paradigms for most of my development work.
Although for games I mainly stick with Object-Oriented programming.
Although for games I mainly stick with Object-Oriented programming.
Quote:Original post by Eriond
Generic programming maybe?
Doesn't that relate more to multi-paradigm programming?
E.g. generic programming an be applied in using a procedural approach (like in the C++ STL algorithms) as well as object-oriented (like C++ STL containers).
Just a thought, I have seen people who refer to it as a stand-alone paradigm as well as a technique applying to multiple paradigms.
--
Pat.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement