Just as food for thought take into account that just silently ignoring what there is past the return statement is error-prone. That is why my opinion would be to be explicit in what you want to do and use comments.<br><br>
What I think a nice change would be is to allow comments inside comments (that is, to only take into account the first and last ' " ' and accept everything that is inside). Maybe comments could be allowed past return statement.
<br><br>0.05<br><br><div class="gmail_quote">On Jan 2, 2008 1:47 PM, Keith Hodges <<a href="mailto:keith_hodges@yahoo.co.uk">keith_hodges@yahoo.co.uk</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br>> Interesting that current compiler barfs on code past the return<br>> statement, saying that there's nothing expected after return.<br>> I don't like such behavior: Sometimes i need to stub-out some code, to
<br>><br></div>I agree with you entirely on this one.<br><br>Does anyone have any idea as to how to implement this?<br><font color="#888888"><br>Keith<br></font><div><div></div><div class="Wj3C7c"><br>> test/debug methods, and i can't simply put ^self in the very beginning
<br>> of method (it forces me to put '[^self] value' instead, just to get<br>> around such 'cleverness' of compiler ).<br>> Very inconvenient and useless feature, as for me, and it can be simply<br>
> replaced by ignoring any input instead.<br>><br>><br>><br><br><br></div></div></blockquote></div><br><br clear="all"><br>-- <br>Saludos,<br>Hernán<br>