<div>Hi Luke,</div><div> </div><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; ">
Really sorry for not giving this any attention for so long.</blockquote><div>No worry... I've been busy with exams for the most of January...</div><div>Though, I hope I had a break through with the newline-<?> bug, yesterday...</div>
<div><br></div><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><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; ">
Removing the brackets from the SmOperNodes was a pretty bad, so they can<br>just go back in.</blockquote><div>Nice :)</div><div><br></div><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; ">
Removing them from UnHor and BinHor also broke some stuff, however, I<br>didn't want to add them back in here, so decided that I would add them<br>with the other nodes types that they were breaking with which seemed to<br>
be BinVer nodes (also the BinDiagonal which is similar).</blockquote><div>Okay, sounds like a great solution... That way we don't get too many brackets...</div><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; ">
Some of the tests are the same kind as the one from last time. It can be<br>a bit difficult to get the right node tree for the test from the parser,<br>which also seems to put in more expression nodes than doing it with the<br>
cursor, which confused me for a bit.</blockquote></div><div>Really neat... Now we'll also get failures if we mess up in cursor...</div><br clear="all">--<br>Regards Jonas Finnemann Jensen.<br>
<br><br><div class="gmail_quote">On Sat, Jan 29, 2011 at 14:01, Luke Dixon <span dir="ltr"><<a href="mailto:6b8b4567@gmail.com">6b8b4567@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi Jonas,<br>
<br>
Really sorry for not giving this any attention for so long.<br>
<div class="im"><br>
> > I've noticed other stuff I've messed up though, so I'm going to continue<br>
> > on this some more :)<br>
> Again I'm not sure you messed it up... It might as well have been<br>
> messed up the first time I wrote it...<br>
> But don't let that stop you from fixing it...<br>
<br>
</div>I'm pretty sure I messed some of it up quite badly, I've attached a<br>
patch that adds some of the brackets back in.<br>
<br>
Removing the brackets from the SmOperNodes was a pretty bad, so they can<br>
just go back in.<br>
<br>
Removing them from UnHor and BinHor also broke some stuff, however, I<br>
didn't want to add them back in here, so decided that I would add them<br>
with the other nodes types that they were breaking with which seemed to<br>
be BinVer nodes (also the BinDiagonal which is similar).<br>
<br>
Some of the tests are the same kind as the one from last time. It can be<br>
a bit difficult to get the right node tree for the test from the parser,<br>
which also seems to put in more expression nodes than doing it with the<br>
cursor, which confused me for a bit.<br>
<br>
Regards,<br>
<font color="#888888">Luke<br>
<br>
<br>
</font></blockquote></div><br>