Reply to thread

Message

<blockquote data-quote="Cadfan" data-source="post: 4835613" data-attributes="member: 40961">I can kind of see it.&nbsp; I've done some recreational programming in an object oriented language.&nbsp; For each item I had to program in the text adventure I was making, there was a sort of stat block.&nbsp; And the sum total of the program, when it was written out in code, was essentially a long list of stat blocks.&nbsp; These stat blocks were heavily laden with key words and references that referred you to other stat blocks.&nbsp;So you might get something that looked kind of like (using an imaginary object oriented programming language):&nbsp;TABLE&nbsp; object, takeable, hideunder, climbon&nbsp; lookDescription &quot;Its a wooden table with a scratch.&quot;&nbsp; tasteDescription &quot;Why are you tasting a table?&nbsp; listenDescription &quot;Tables don't make noise.&quot;&nbsp; if HIT TABLE, then &quot;The table smashes into splinters.&quot;, add SPLINTERS to KITCHEN;&nbsp;And then things would continue with the next object. &nbsp;I can kind of see how power lists might feel that way, particularly in the way that reading a single object tells you very little about the overall function of the code, and you have to read them all and understand them in the context of one another to get a *feel* for what's going on.&nbsp;Its not a strong analogy, but I can see it.</blockquote>

[QUOTE="Cadfan, post: 4835613, member: 40961"] I can kind of see it. I've done some recreational programming in an object oriented language. For each item I had to program in the text adventure I was making, there was a sort of stat block. And the sum total of the program, when it was written out in code, was essentially a long list of stat blocks. These stat blocks were heavily laden with key words and references that referred you to other stat blocks. So you might get something that looked kind of like (using an imaginary object oriented programming language): TABLE object, takeable, hideunder, climbon lookDescription "Its a wooden table with a scratch." tasteDescription "Why are you tasting a table? listenDescription "Tables don't make noise." if HIT TABLE, then "The table smashes into splinters.", add SPLINTERS to KITCHEN; And then things would continue with the next object. I can kind of see how power lists might feel that way, particularly in the way that reading a single object tells you very little about the overall function of the code, and you have to read them all and understand them in the context of one another to get a *feel* for what's going on. Its not a strong analogy, but I can see it. [/QUOTE]

Verification