A little while back, I wrote in a review in a review of a Ruby bowling sim that I might try my hand at modelling the game myself, focussing on the funky "deferred scores" system. Since a2bfay, who posted the original question, has since posted a thoroughly updated piece of code thoroughly updated piece of code, I figured I'd better get mine finished, especially since I chose a very different approach. I just figured it'd be fun to put up for review. The main point for me was mostly to do some plain ol' Ruby for fun and zero profit. It's a self-imposed programming-challenge, I suppose.
A little while back, I wrote in a review of a Ruby bowling sim that I might try my hand at modelling the game myself, focussing on the funky "deferred scores" system. Since a2bfay, who posted the original question, has since posted a thoroughly updated piece of code, I figured I'd better get mine finished, especially since I chose a very different approach. I just figured it'd be fun to put up for review. The main point for me was mostly to do some plain ol' Ruby for fun and zero profit. It's a self-imposed programming-challenge, I suppose.
A little while back, I wrote in a review of a Ruby bowling sim that I might try my hand at modelling the game myself, focussing on the funky "deferred scores" system. Since a2bfay, who posted the original question, has since posted a thoroughly updated piece of code, I figured I'd better get mine finished, especially since I chose a very different approach. I just figured it'd be fun to put up for review. The main point for me was mostly to do some plain ol' Ruby for fun and zero profit. It's a self-imposed programming-challenge, I suppose.
1) I should have been clearer. I do not intend for this single class to do and be everything, even if it does do a lot. To more fully model a game, you'd still need something like a Game class, perhaps a Player class, etc..
1) I should have been clearer. I do not intend for this single class to everything, even if it does do a lot. To more fully model a game, you'd still need something like a Game class, perhaps a Player class, etc..
1) I should have been clearer. I do not intend for this single class to do and be everything, even if it does do a lot. To more fully model a game, you'd still need something like a Game class, perhaps a Player class, etc..
So it doesn't leave much for other classes to do1. Not necessarily a bad thing, of course.
Edits & addenda:
1) I should have been clearer. I do not intend for this single class to everything, even if it does do a lot. To more fully model a game, you'd still need something like a Game class, perhaps a Player class, etc..
So it doesn't leave much for other classes to do. Not necessarily a bad thing, of course.
So it doesn't leave much for other classes to do1. Not necessarily a bad thing, of course.
Edits & addenda:
1) I should have been clearer. I do not intend for this single class to everything, even if it does do a lot. To more fully model a game, you'd still need something like a Game class, perhaps a Player class, etc..