Hi Tim,
> The suggestion is that Sage consider an Axiom Category-like organization
> that normalizes the names through inheritance. Of course, this requires
> a huge re-think of the organization of Sage. It would also require "cover"
> functions for external packages to map the names to t
>> I like s.cardinality() since that's what I've used often already all
>> over in Sage.
>> Do
>>
>> sage: search_src('cardinality')
>>
>
>Arglll !!! I had this idea and issued an
>
>tomahawk-*ge-combinat/sage $ grep def\ cardinality\( **/*.py* | wc
> 11 35 533
>
>which was a pretty
Jason Grout wrote:
> I think in general, the definition goes with the most descriptive name
> (e.g., cardinality). Sometimes a shorter alias is then created to make
> typing easier (e.g., card). An example of this the adjacency matrix of
> a graph. We have g.adjacency_matrix, but we also have
Florent Hivert wrote:
> Dear William
>
>> I like s.cardinality() since that's what I've used often already all
>> over in Sage.
>> Do
>>
>> sage: search_src('cardinality')
>>
>
> Arglll !!! I had this idea and issued an
>
> tomahawk-*ge-combinat/sage $ grep def\ cardinality\( **/*.py* |
Dear William
> I like s.cardinality() since that's what I've used often already all
> over in Sage.
> Do
>
> sage: search_src('cardinality')
>
Arglll !!! I had this idea and issued an
tomahawk-*ge-combinat/sage $ grep def\ cardinality\( **/*.py* | wc
11 35 533
which was a
Couldn't we define something like :
def _len_(self):
return ...
that behave like we want as it is done for _str_ and _repr_ ?
Sébastien Labbé
LaCIM, Montréal
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscrib
On Wed, Feb 25, 2009 at 2:43 PM, Florent Hivert
wrote:
>
> Dear All,
>
> We working in combinat have a problem of naming convention which is likely to
> concern everyone in sage. As you can guess, in combinatorics we like to count
> sets an iterate through them. So we designed some objects c
