<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 24 Jan 2010, at 19:19, Andreas Raab wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Igor Stasenko wrote:<br><blockquote type="cite">2010/1/24 keith <<a href="mailto:keith_hodges@yahoo.co.uk">keith_hodges@yahoo.co.uk</a>>:<br></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I look forward to seeing trunk with MC1.5 then, cool<br></blockquote></blockquote><blockquote type="cite">if you remember, i already raised this topic here and in Pharo list.<br></blockquote><blockquote type="cite">The problem is, that (as you pointing in another thread about<br></blockquote><blockquote type="cite">capturing knowledge), there's no one left,<br></blockquote><blockquote type="cite">having such knowledge about MC 1.5., to do such integration.<br></blockquote><br>We did the experiment earlier:<br><br><a href="http://lists.squeakfoundation.org/pipermail/squeak-dev/2009-October/140345.html">http://lists.squeakfoundation.org/pipermail/squeak-dev/2009-October/140345.html</a><br><br>The problem is that MC 1.5 and 1.6 appear to be buggy in various areas and don't appear ready for prime time.<br><br>Cheers,<br> - Andreas<font class="Apple-style-span" color="#000000"><font class="Apple-style-span" color="#144FAE"><br></font></font></div></blockquote><br></div><div>I have been using them for years now without trouble. </div><div><br></div><div>How you cope with the old MC I dont know. I cant use it, it looses overides, and you have to maintain a separate image for every package you contribute to.</div><div><br></div><div>MC1.6 should be less buggy, if traits support was finished.</div><div><br></div><div>Keith</div></body></html>