Nicolas Borie <nicolas.bo...@math.u-psud.fr> writes: > From my point of view, the problem is the following : You have a > Constructor or SetFactory which have a lot of possible arguments and > your code have to dealt with combination of arguments that make your > set empty:
> (1) - I consider each argument as a mathematical condition thus if two > arguments make the set empty, it is the problem of the user and I return > the EmptySet (better than the empty list, doing the same than the empty > list but category compatible). My personal preference is for that one, because in my experience it is usually easier to generate the empty set than to check for absurdities. Martin -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en.