Data-oriented design: Difference between revisions

Revision as of 00:49, 14 June 2016

Revision as of 20:47, 17 June 2016

Line 12:

The claim is that traditional [[object-oriented]] design principles result in poor data locality, especially if [[runtime polymorphism]] is used (which itself is especially problematic on certain processors).

<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 does superficially seem to 'organise code around data', the practice is quite different. OOP is actually about organising [[source code]] around [[data types]], rather than making thephysically grouping of individual fields and arrays convenientin a manner that is efficient for access by specific functions. It also frequently hides layout details under [[abstraction layer]]s, whilst a data-oriented programmer wants to think about this first and foremost.

== Other languages ==