> no, the 3rd element is computed using a different meaning of (1,2) than > the one used to compute the 2nd one. > If you used the same meaning for the 2nd as the one for the 3rd, your > 2nd would be (1,1).
Then how is your input of type "Tuple of Tuple", sir ? > OK, great, so (1,2) is not an element. > Yet, you take (1,2) as an element when you compute the 3rd element of > the orbit. Is your implementation of the function going to read your > mind, to work correctly? Of course, because the type of the value returned is "A list of tuple of tuple". Hence everything at depth <= 3 is a container,and everything at depth 4 is an element. Nathann -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
