<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On 16 Feb 2014, at 14:07, Sven Van Caekenberghe <<a href="mailto:sven@stfx.eu">sven@stfx.eu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;">This not an incompatibility between Pharo 2 and 3. Instead of creating a new package, it could also be fixed with a little dynamic hack.</span></blockquote></div><br><div>Though I’m always amazed that deprecated methods immediately break things in Pharo.</div><div>They’re supposed to keep working until the next version, but the ‘raise a blocking dialog’ setting that is on by default in Pharo makes it break immediately.</div><div><br></div><div>Johan</div></body></html>