Implicit lists
Christian Tismer
tismer at tismer.com
Fri Jan 31 08:41:47 EST 2003
More information about the Python-list mailing list
Fri Jan 31 08:41:47 EST 2003
- Previous message (by thread): Implicit lists
- Next message (by thread): Implicit lists
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Christian Tismer wrote: > Delaney, Timothy wrote: > >> From: Christian Tismer [mailto:tismer at tismer.com] >> >> In my opinion, the crux of this all is the decision >> that strings are iterable. >> The number of use cases which I have seen so far is much >> shorter than this thread. >> Strings are much more often used as solid objects. >> I'm pretty sure Guido would remove the sequence-ness >> of strings in Python 3000, even to avoid this kind >> of problems. Sorry about that statement! It doesn't make sense, since sequence behavior is needed for string indexing and slicing, and these are of course necessary. The real difference between strings IMHO is that strings are no containers for objects. I think this is similar to array.array objects, which also would be considered a single parameter. What we really need seems to be a criterion if something is a container or not. ciao - chris
- Previous message (by thread): Implicit lists
- Next message (by thread): Implicit lists
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list