Revision as of 11:30, 30 September 2021 edit Alexander Davronov (talk \| contribs) Extended confirmed users 10,942 edits →Contrast with object orientation: See Talk:Data-oriented_design#Contrast with object orientation Tag: Visual edit ← Previous edit		Revision as of 11:51, 30 September 2021 edit undo AnomieBOT (talk \| contribs) Bots 6,856,328 edits m Dating maintenance tags: {{Original research section}} Next edit →
Line 9: == Contrast with object orientation == {{Original research section\|date=September 2021}} The claim is that traditional [[object-oriented programming]] (OOP) design principles result in poor data locality,{{Clarify\|reason=What? Sorry, but OOP doesn't have to do anything with data layouts or design. Data are instances of the Objects and can be organized irrelevantly to OOP itself. The whole paragraph make no sense.\|date=September 2021}} more so if runtime polymorphism ([[dynamic dispatch]]) is used (which is especially problematic on some processors).<ref>{{cite web\|title=What's wrong with Object-Oriented Design? Where's the harm in it?\|url=http://www.dataorienteddesign.com/dodmain/node17.html}}describes the problems with virtual function calls, e.g., i-cache misses</ref><ref>{{cite web\|title=Data-oriented design - why you might be shooting yourself in the foot with OOP\|url=http://gamesfromwithin.com/data-oriented-design}}</ref> Although OOP appears to "

Data-oriented design: Difference between revisions