Message5988

Author zyasoft
Recipients JonathanFeinberg, zyasoft
Date 2010-08-18.03:16:09
SpamBayes Score 2.4210144e-07
Marked as misclassified No
Message-id <1282101370.69.0.287602485035.issue1645@psf.upfronthosting.co.za>
In-reply-to
Content
I think I understand why you'd want to construct mutable versions of these types for something like processing.py, but two cautions if this is representative of your code:

1) Obviously objects of these types are no longer hashable as such and thus will really screw things up if they're placed in a Map. You may want to change their hashCode to be on their object identity, or throw a TypeError, like PyList.

2) Normally you should consider making the underlying fields volatile.

Mutation likely impacts PyString/PyUnicode even more.
 
Also, the current field in PyString is string, so should it be getValue or getString? I tend to favor the latter form this moment.
History
Date User Action Args
2010-08-18 03:16:10zyasoftsetmessageid: <1282101370.69.0.287602485035.issue1645@psf.upfronthosting.co.za>
2010-08-18 03:16:10zyasoftsetrecipients: + zyasoft, JonathanFeinberg
2010-08-18 03:16:10zyasoftlinkissue1645 messages
2010-08-18 03:16:09zyasoftcreate