Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!feeds.phibee-telecom.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!npeer03.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
From: 88888 Dihedral <dihedral88888@googlemail.com>
Newsgroups: comp.lang.python
Subject: Re: copy on write
Date: Fri, 3 Feb 2012 14:16:45 -0800 (PST)
Organization: http://groups.google.com
Lines: 16
Message-ID: <7136289.998.1328307405342.JavaMail.geo-discussion-forums@prhq15>
References: <mailman.4709.1326455724.27778.python-list@python.org> <4f101f45$0$29999$c3e8da3$5496439d@news.astraweb.com> <CAPTjJmr-069xisN6h4Cxt77vWbb+VhtMb-LRNfvyphwGz0C5GA@mail.gmail.com> <mailman.4714.1326462667.27778.python-list@python.org> <jephmt$hhp$1@reader1.panix.com> <mailman.4718.1326473361.27778.python-list@python.org> <9nb5ubFu17U2@mid.individual.net> <mailman.4728.1326486286.27778.python-list@python.org> <9nblhhFr5bU1@mid.individual.net> <mailman.4736.1326498530.27778.python-list@python.org>
Reply-To: comp.lang.python@googlegroups.com
NNTP-Posting-Host: 123.204.77.169
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Trace: posting.google.com 1328307787 21946 127.0.0.1 (3 Feb 2012 22:23:07 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Fri, 3 Feb 2012 22:23:07 +0000 (UTC)
Cc: python-list@python.org
In-Reply-To: <mailman.4736.1326498530.27778.python-list@python.org>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=123.204.77.169; posting-account=5JdMBQoAAABHnS4mjpqEzxnmWtgiiVNw
User-Agent: G2/1.0
X-Google-Web-Client: true
Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:19921

=E5=9C=A8 2012=E5=B9=B41=E6=9C=8814=E6=97=A5=E6=98=9F=E6=9C=9F=E5=85=ADUTC+=
8=E4=B8=8A=E5=8D=886=E6=97=B648=E5=88=8629=E7=A7=92=EF=BC=8CEvan Driscoll=
=E5=86=99=E9=81=93=EF=BC=9A
> On 01/13/2012 03:20 PM, Neil Cerutti wrote:
> > They perform the same action, but their semantics are different.
> > operator+ will always return a new object, thanks to its
> > signature, and operator+=3D shall never do so. That's the main
> > difference I was getting at.

Well, in any associative operation with an identity implemented in a comput=
er language  personally I believe the operator overloading part in C++ is  =
 another teasing trick.

=20
Do we have to work out the algebra here?