A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2002-May/023879.html below:

[Python-Dev] Re: [bug?] UserLong.py - pow(5, UserLong(3), 26) fails

[Python-Dev] Re: [bug?] UserLong.py - pow(5, UserLong(3), 26) failsMichael Hudson mwh@python.net
01 May 2002 19:56:15 +0100
Luke Kenneth Casson Leighton <lkcl@samba-tng.org> writes:

> michael,
> 
> the point of doing a UserLong.py is that it is an easy way
> to add in profiling and debug info and to evaluate alternative
> implementations of Long numbers.
> 
> the ultimate aim is to find out if it is worth adding in
> support for Aspex Technology's massively parallel signal
> processor chip as a python co-processor.

I see.

Another idea: make UserLong a "new-style class".  I'm not sure what
this changes, but it changes "stuff" in this area...

Cheers,
M.

-- 
  C is not clean -- the language has _many_ gotchas and traps, and
  although its semantics are _simple_ in some sense, it is not any
  cleaner than the assembly-language design it is based on.
                                        -- Erik Naggum, comp.lang.lisp




RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4