<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On May 9, 2008, at May 9:7:57 AM, Greg Ewing wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">* I have streamlined the integer for-loop syntax. Instead</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span class="Apple-converted-space"> </span>of the loop variable redundantly appearing in two places,</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span class="Apple-converted-space"> </span>it's now just</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span class="Apple-converted-space"> </span>for x < i < y:</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span class="Apple-converted-space"> </span>...</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><br></div></blockquote><br></div><div>Not that my opinion matters a whole lot, but I prefer the redundant syntax. This new syntax solves a problem, and introduces a problem which (in my opinion) is worse. In python, I am used to syntax:</div><div><br></div><div>for var in stuff:</div><div><br></div><div>where my eye finds "var" and then "stuff", so I first find out the relevant variable, and then the values it will take.</div><div><br></div><div>in old pyrex syntax, </div><div><br></div><div>for var in begin<= var < end: </div><div><br></div><div>my eye finds "var" and then "begin" and "end", so I first find out the relevant variable, and then the values it will take.</div><div><br></div><div>In the new syntax, </div><div><br></div><div>for begin <= var < end:</div><div><br></div><div>my eye finds some values of var, then the relevant variable, then the end. It changes the logic of the for-loop organization in my head, and as I read. It makes it less like Python, and thus more jarring to go between the two. </div><div><br></div><div>Personally, I never minded the redundancy (how much extra typing is it really?)</div><div><br></div><div>I find breaking readability, and a parallel with existing python syntax to be far far worse. I hope you keep the two syntaxes, and see what the response is when developers actually use it for a while. My gut feeling is that the new syntax will not be favored, but I could very well be wrong.</div><div><br></div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Just my 2c<br></div><div><br></div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>thanks,<br></div><div><br></div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Brian Blais<br></div><div><br></div><div><br></div><div> <span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Monaco; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><div>-- </div><div>Brian Blais</div><div><a href="mailto:bblais@bryant.edu">bblais@bryant.edu</a></div><div><a href="http://web.bryant.edu/~bblais">http://web.bryant.edu/~bblais</a></div><div><br class="khtml-block-placeholder"></div><br class="Apple-interchange-newline"></span> </div><br></body></html>