#17392: Make list of built-in normal form games
-------------------------------------+-------------------------------------
       Reporter:  kcrisman           |        Owner:
           Type:  enhancement        |       Status:  needs_review
       Priority:  minor              |    Milestone:  sage-6.8
      Component:  game theory        |   Resolution:
       Keywords:  days64             |    Merged in:
        Authors:  Vincent Knight,    |    Reviewers:  Karl-Dieter Crisman,
  James Campbell                     |  Travis Scrimshaw
Report Upstream:  N/A                |  Work issues:
         Branch:                     |       Commit:
  u/vinceknight/catalog_of_games     |  31ec186babfd107ca4f1ce62a513a7fe235d557c
   Dependencies:                     |     Stopgaps:
-------------------------------------+-------------------------------------

Comment (by kcrisman):

 > > starts looking a little longish.  Was there a reason for doing that
 uniformly?
 >
 > Do you mean the multilines? That's mainly to stick with the 79 character
 limit, I noticed this for the larger games and then thought I should do it
 throughout. I agree that it looks pretty bad. I'm happy to leave as is (so
 that it fits with the 79 characters strictly) but perhaps the rule could
 be broken for some of the smaller dicts?

 I think only do it if you really go well beyond the limit.  Or just
 continue the multiline in such a way that there are TWO lines and not
 EIGHT lines :)

 > > You may also want to (briefly) mention somewhere convenient why you're
 doing this, or perhaps just where the utility dictionary is `==` to the
 game, which I wasn't expecting (since it's not a game, just a random
 dictionary) but is fine, as far as I care about it.
 >
 > So perhaps mention something a long the lines of:
 >
 > {{{
 > sage: # Building a dictionary to test the required result
 > sage: # The order of the dictionary might differ on a given machine
 > sage: d = {...
 > sage: d == g
 > }}}

 Oh, not even that much - maybe just before the very first instance of
 this, preferably not within a specific function but at the module level,
 something like

 {{{
 We can construct a game::

     sage: construct a game
     sage: do something with it

 When we test whether the game is actually the one in question, sometimes
 we will build a dictionary to test it, since this can be platform-
 dependent, like so::

     sage: d = {...
     sage: d == g
     True
 }}}
 And then the others are tacit.

--
Ticket URL: <http://trac.sagemath.org/ticket/17392#comment:70>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to