RetroSearch Browse

Mon Apr 30 14:48:58 EDT 2001 · http://mail.python.org/pipermail/python-list/2001-April/077536.html

Brian Kelley wrote:
> 
> Anyway, it seems like I can avoid the whole problem by renaming mx.Number.Integer
> as "BitVector" This is what I am using this structure for anyway.  Then I can
> avoid all of these problems.  So let me ask this question, would anyone mind a
> contributed type BitVector to mx.Number?  Then I can add all of the fun stuff
> like Tanimoto, Euclidean and Jaccard distances...

If you can come up with well-defined interfaces for these -- go ahead.

BTW, do you want to implement these in C or in Python ?

-- 
Marc-Andre Lemburg
______________________________________________________________________
Company & Consulting:                           http://www.egenix.com/
Python Software:                        http://www.lemburg.com/python/

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-list/2001-April/077536.html below:

ANN: mxNumber -- Experimental Number Types, Version 0.2.0