<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On 25.02.2010, at 01:52, Eliot Miranda wrote:</div><blockquote type="cite"><br><br><div class="gmail_quote">On Wed, Feb 24, 2010 at 4:20 PM, Nicolas Cellier <span dir="ltr"><<a href="mailto:nicolas.cellier.aka.nice@gmail.com">nicolas.cellier.aka.nice@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; ">
Lukas suggested to not provide backward compatibility and compile 1@-2<br>
as 1 @- (2)<br></blockquote><div>This should be done anyway. But IMO @- should be implemented to raise an error /not/ sign-invert! We want people to clean up, not rely on a crutch.</div>
</div></blockquote></div><div><br></div><div>I for one would hate if I could't type -1@-1 interactively anymore. This syntax is so common and used almost as if it was a literal that I strongly feel @- should be implemented to do the expected (and Point's printOn: should generate text without parens).</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: Lucida Grande; font-size: 12px; 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 style="font-family: Helvetica; "><span class="Apple-style-span" style="font-family: Helvetica; ">- Bert -</span></div><br class="Apple-interchange-newline"></span>
</div>
<br></body></html>