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/2000-March/002942.html below:

Do we need a UserString class?

[Python-Dev] [1.6]: UserList, Dict: Do we need a UserString class?Moshe Zadka Moshe Zadka <mzadka@geocities.com>
Wed, 29 Mar 2000 11:59:47 +0200 (IST)
On Wed, 29 Mar 2000, Peter Funk wrote:

> Hi!
> 
> Moshe Zadka:
> > eagerly-waiting-for-UserString.py-ly y'rs, Z.
> 
> Well, I've added the missing methods.  Unfortunately I ran out of time now and
> a 'test_userstring.py' derived from 'src/Lib/test/test_string.py' is still 
> missing.  

Great work, Peter! I really like UserString. However, I have two issues
with MutableString:

1. I tshouldn't share implementation with UserString, otherwise your
algorithm are not behaving with correct big-O properties. It should
probably use a char-array (from the array module) as the internal
representation.

2. It shouldn't share interface iwth UserString, since it doesn't have a
proper implementation with __hash__.


All in all, I probably disagree with making MutableString a subclass of
UserString. If I have time later today, I'm hoping to be able to make my
own MutableString




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