Closed GoogleCodeExporter closed 9 years ago
A package rules and the classes Limit,NoLimit and PotLimit have been added and
implemented to provide this functionality. The type of betting rules is
currently
chosen in the constructor of GameControl.
The subclasses of BettingRules provide information about whether a certain bet
or
raised is allowed and if they are not allowed, they contain the reason why.
If anyone else could check the code for errors or inclarities... No test
classes for
now maybe later.
Choosing the betting rules could be made easier fi by adding a string with the
name
of the rules to the GameControl constructor. If you'd give some feedback about
this?
Original comment by cuypers....@gmail.com
on 12 Jul 2007 at 4:45
I have just checked your code. I see you have implemented every thing in game
property, which is a nice thing.
I believe the constructor of game should be provided with the game property as
argument (where the game property was intended for, but not yet implemented).
Then
you won't need a string argument to choose between limits. It's always the
property
that changes from game to game. Remember an oo-design guideline: encapsulate
what
changes :).These settings can be chosen by a host for example at initialisation
of a
game, with the maximum bets, blinds,...
Original comment by kenzotom...@gmail.com
on 12 Jul 2007 at 7:11
Original comment by kenzotom...@gmail.com
on 12 Jul 2007 at 7:12
Original comment by guy...@gmail.com
on 21 Jul 2007 at 4:34
Original issue reported on code.google.com by
guy...@gmail.com
on 12 Jul 2007 at 2:39