Reply to thread

Message

<blockquote data-quote="azhrei_fje" data-source="post: 4104678" data-attributes="member: 12966">Thank you for posting your code!&nbsp; I don't know C#, but I have a mild curiosity of what the language looks like, so I appreciate having a class that I can understand its function. <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":)" title="Smile&nbsp; &nbsp; :)"&nbsp; data-smilie="1"data-shortname=":)" />Having said that, I would like to point out that in a true object-oriented design, this implementation would likely need to change somewhat.For example, the class should not be deciding how the data is returned to the caller.&nbsp; Instead, the caller should register a &quot;callback&quot; function and your class would then call that function either multiple times with each die result passed as a parameter each time, or a single time with a list of values passed as an array/linked list/etc.I can explain further, if you'd like, or you can check out the book Design Patterns by the Gang of Four (the only one I can ever remember is Gamma; look it up on Amazon thought and you'll find it quickly).&nbsp; One of the chapters is on the Observer/Observable design pattern and that pattern is a really good idea for a dice rolling class.&nbsp; In fact, when I teach OOA&amp;D and get to chapter on design patterns, I often use the dice roller as an example of this pattern.&nbsp; Taken to its logical extreme, the output is completely decoupled from the class itself, allowing an entire hierarchy of classes which implement the callback method.Anyway, as I mentioned at the beginning, thanks for the code snippet.&nbsp; I'm looking forward to perusing it in detail. <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":)" title="Smile&nbsp; &nbsp; :)"&nbsp; data-smilie="1"data-shortname=":)" /></blockquote>

[QUOTE="azhrei_fje, post: 4104678, member: 12966"] Thank you for posting your code! I don't know C#, but I have a mild curiosity of what the language looks like, so I appreciate having a class that I can understand its function. :) Having said that, I would like to point out that in a true object-oriented design, this implementation would likely need to change somewhat. For example, the class should not be deciding how the data is returned to the caller. Instead, the caller should register a "callback" function and your class would then call that function either multiple times with each die result passed as a parameter each time, or a single time with a list of values passed as an array/linked list/etc. I can explain further, if you'd like, or you can check out the book [i]Design Patterns[/i] by the Gang of Four (the only one I can ever remember is Gamma; look it up on Amazon thought and you'll find it quickly). One of the chapters is on the Observer/Observable design pattern and that pattern is a really good idea for a dice rolling class. In fact, when I teach OOA&D and get to chapter on design patterns, I often use the dice roller as an example of this pattern. Taken to its logical extreme, the output is completely decoupled from the class itself, allowing an entire hierarchy of classes which implement the callback method. Anyway, as I mentioned at the beginning, thanks for the code snippet. I'm looking forward to perusing it in detail. :) [/QUOTE]

Verification