Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.freenet.ag!ecngs!feeder2.ecngs.de!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed1a.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
Reply-To: jw14896.2014@my.bristol.ac.uk
Date: Fri, 27 Mar 2015 20:24:24 +0000
Subject: Proposal for new minor syntax
From: Jamie Willis <jw14896.2014@my.bristol.ac.uk>
To: python-list@python.org
Content-Type: multipart/alternative; boundary=047d7bd767200f90a605124aeb6a
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.275.1427487867.10327.python-list@python.org>
Lines: 66
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:88181

--047d7bd767200f90a605124aeb6a
Content-Type: text/plain; charset=UTF-8

I would like to propose a new piece of syntax for the python language; .=

In short, the operator is form of syntactic sugar, for instance consider
the following code:

hello = "hello world              "
hello = hello.strip()

This could be written as:

hello = "hello world              "
hello .= strip()

In this slightly contrived example, the programmer saved (a small amount
of) time when writing the code. With code with longer variable names, or
lots of similar statements all in a row, this helps to keep code more
concise.

The operator would be constricted to one method or field on the right-hand
side, which must belong to the object on the left hand side.

Another example could be when using Linked Lists, instead of writing
something like:

loop_node = loop_node.next

you could write:

loop_node .= next

Does this idea have any chance of acceptance if submitted as a PEP? What
are the potential concerns I could consider with the syntax?

Thanks,

Jamie

--047d7bd767200f90a605124aeb6a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I would like to propose a new piece of syntax for the pyth=
on language; .=3D<div><br></div><div>In short, the operator is form of synt=
actic sugar, for instance consider the following code:</div><div><br></div>=
<div>hello =3D &quot;hello world =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0&quot;</div><div>hello =3D hello.strip()</div><div><br></div><div>Thi=
s could be written as:</div><div><br></div><div>hello =3D &quot;hello world=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;</div><div>hello .=
=3D strip()</div><div><br></div><div>In this slightly contrived example, th=
e programmer saved (a small amount of) time when writing the code. With cod=
e with longer variable names, or lots of similar statements all in a row, t=
his helps to keep code more concise.=C2=A0</div><div><br></div><div>The ope=
rator would be constricted to one method or field on the right-hand side, w=
hich must belong to the object on the left hand side.</div><div><br></div><=
div>Another example could be when using Linked Lists, instead of writing so=
mething like:<br><br></div><div>loop_node =3D loop_node.next</div><div><br>=
</div><div>you could write:</div><div><br></div><div>loop_node .=3D next</d=
iv><div><br></div><div>Does this idea have any chance of acceptance if subm=
itted as a PEP? What are the potential concerns I could consider with the s=
yntax?</div><div><br></div><div>Thanks,</div><div><br></div><div>Jamie</div=
></div>

--047d7bd767200f90a605124aeb6a--