Reply to thread

Message: <blockquote data-quote="FormerlyDickensC" data-source="post: 4104816" data-attributes="member: 53954">my apologies for getting on a rant here, buuuuuuuuut.......dude...it rolls dice.....and its a static method, thats all. using delegates (or call back methods) is overkill for such a simple piece of code.  The vast majority of the code is simply parsing the string. If you want to have the method sometimes return an int and sometimes a string..then just overload it or create multiple methods..or use the 'out' keyword. (my fault, you said you weren't familiar with C#). But I think you said you were writing a WPF app, so you should be familiar with .NET, right? or was that someone else?but the point of the method was to parse the die roll string..you mentioned that your delegate would pass in each die roll or an array of rolls...well if they're already parsed from the input string then there is no need for the method. just instantiate your own Random object and roll directly. I'm fully versed in the Observer pattern, I must argue that your use of it as you explained is not what I would consider the most efficient. Calling various delegate (or callback) methods is the same as calling overloads, and is unnecessary. It introduces complexity where there need be none.  .....ummmm no. maybe if we were dealing with a highly diversified object model then that would be appropriate.  But we're not. We're dealing with strings, int's, and one little method. Look, I'm not trying to pick an argument or be a pain or a jerk. But implementing the pattern in the way you explain is really not necessary or helpful.  Bottom Line: There are only two possible types the caller would want the data returned as....a string or an int. The best answer, imo, is simply return as int and let the caller cast to string as needed. Simple. Elegant. No need for delegates. Besides, the caller is not observing anything. The caller is not waiting for something to happen on the part of the dice roller. The caller simply wants a result from his given input. Applying the Observer pattern is nonsensical in this case. Be careful how you implement grand ideas. Sometimes, you just need to do what you have to do, and no more. Plus I didn't write the code or algorithm, I translated it from Java that another person posted here. I left the algorithm intact.  Remember the major point of the method is to parse text. Take a look at my explanation in the first post. If you teach analysis and design, answer this question that I came across: <a href="http://forums.microsoft.com/MSDN/ShowPost.aspx?siteid=1&PostID=2994966" target="_blank">http://forums.microsoft.com/MSDN/ShowPost.aspx?siteid=1&PostID=2994966</a>Again, I apologize for my rudeness if that is how I'm coming across. It is not my intention.</blockquote>

Verification