The rest of the chapter weighs the pros and cons of using "objects" versus using "data structures" and the importance of not mixing the two concepts in a single class Not mentioned in the chapter: a single actual data structure
Show this thread
"Clean Code", chapter "Objects and Data Structures". Here we learn that a /data structure/ is something which exposes its data and has no meaningful functions, as opposed to an /object/, which exposes methods/abstractions of its data. That's the difference, apparentlypic.twitter.com/YGCkc4Ve4D
-
-
-
I guess if you understand "data structure" to mean the equivalent of "struct", this makes marginal sense? It's easy enough to confuse those terms...?pic.twitter.com/OoWuD4w8un
Show this thread -
It was a startlingly short and confusing chapter. Other than mentioning the Law of Demeter this is essentially its full content
Show this thread -
I'm not all the way through it yet. But yeah, it's shaping up to be a fairly weak offering. In our reading group I'm mainly using it as a launching point for more detailed and specific advicehttps://twitter.com/OleenaNatiras/status/1106148152040742912 …
Show this thread
End of conversation
New conversation -
-
-
I'm trying to think of a language that has a genuine, enforceable difference between the two and I'm coming up empty. Even then, I'd say structures are a subset of objects.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.