<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, May 2, 2014 at 9:20 AM, Chris Muller <span dir="ltr"><<a href="mailto:asqueaker@gmail.com" target="_blank">asqueaker@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Eliot, could this be the cause of Dave's "RemoteString" problem the other week?<br></blockquote><div><br>
</div><div>I don't know.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Is this problem new to 4.5 or did it also exist in 4.4?<br></blockquote><div><br></div><div>It's ancient.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
It's sounding more and more like we're going to need a 4.5.1. So far we have:<br>
<br>
- Chinese character issue<br>
- Saving projects issue<br>
- 'Smalltalk' Environment issue<br>
- this?<br></blockquote><div><br></div><div>One position would be to ask "Isn't that what trunk is?". But for the noob or the industrial user (or anyone who wants a defined starting position, for example me in autobuilding the VMMaker image) I think providing defined named entities makes sense.</div>
<div><br></div><div>So another position (which appeals to me) is to decide to take 4.5, and on, say, the first of each month, update it and publish the updated thing as 4.5.N where N ranges from 1 to 12 or beyond. Hopefully 4.6/5 will come along before we get to 13 ;-)</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
2014-05-02 11:11 GMT-05:00 Eliot Miranda <<a href="mailto:eliot.miranda@gmail.com">eliot.miranda@gmail.com</a>>:<br>
<div class="HOEnZb"><div class="h5">> Hi Colin, Hi All,<br>
><br>
> if in 4.5 one tries to evaluate a doit somewhere in a verdant<br>
> transcript, one containing much content, then too much logging will occur to<br>
> the changes file. Instead of the selected doit being logged, the entire<br>
> contents of the transcript up to the end of the doit will be logged, and<br>
> that can cause parse errors when recovering changes.<br>
><br>
> So how best to solve this? Here are some ideas and I wanted to ask people's<br>
> opinion<br>
><br>
> - have CompilationCue remember the position of the source stream and instead<br>
> of using "source contents" in streamToLog use "source position; upToEnd"<br>
><br>
> - have Parser/Scanner remember the characters parsed in a buffer and take<br>
> them from there<br>
><br>
> - change ReadWriteStream to remember its initial position so that when one<br>
> says<br>
> (ReadWriteStream on: (String withAll: ((0 to: 255) collect: [:n| n<br>
> asCharacter]))<br>
> from: $A asInteger + 1 to: $Z asInteger + 1) contents<br>
> one gets 'ABCDEFGHIJKLMNOPQRSTUVWXYZ'<br>
> instead of<br>
> '<br>
> !"#$%&''()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ'<br>
><br>
> IMO the last option is the right thing to do but it feels like a big change.<br>
> --<br>
> best,<br>
> Eliot<br>
><br>
><br>
><br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>best,<div>Eliot</div>
</div></div>