Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

14
  • 2
    The main alternative to class-based OO, prototype-based OO, also seems to couple data and behaviour. Actually, it seems to differ from ECS just as much as class-based OO does. So could you elaborate what you mean by OO? Commented Sep 17, 2013 at 14:23
  • To add on to @delnan's question, are you disagreeing with the snippet of the OO wikipedia article I quoted? Commented Sep 17, 2013 at 16:32
  • @tieTYT: The Wikipedia quote is talking about encapsulation and information hiding. I don’t think it is evidence that data–behaviour coupling is required, only that it is common. Commented Sep 17, 2013 at 17:31
  • @delnan: I don’t mean anything by OO. Object-oriented programming, to me, is exactly what it says on the tin: programming with “objects” (as opposed to functions, rules, actors, dataflow combinators, etc.) where the particular definition of object is implementation-defined. Commented Sep 17, 2013 at 17:34
  • 1
    @tieTYT: I was just describing implementations I’ve seen in the wild, in order to convey that it’s a broad term—not contradictory to, but certainly broader than, the Wikipedia description. Commented Sep 17, 2013 at 19:38