<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body ><div style='font-size:10pt;font-family:Verdana,Arial,Helvetica,sans-serif;'><div>Hi Eliot.<br></div><div><br></div><div><br><blockquote style="border-top-color: rgb(204, 204, 204); border-left-color: rgb(204, 204, 204); border-right-color: rgb(204, 204, 204); border-bottom-color: rgb(204, 204, 204); border-top-width: 1px; border-left-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-top-style: solid; border-left-style: solid; border-right-style: solid; border-bottom-style: solid; padding-top: 7px; padding-right: 7px; padding-bottom: 7px; padding-left: 7px; background-color: rgb(245, 245, 245);"><div>---- On Sat, 10 May 2014 11:27:30 -0700 <b>Eliot Miranda<eliot.miranda@gmail.com></b> wrote ---- </div><div><br></div><div>... </div><div><br></div><div>+1. But I recommend a compatibility package that is loaded alongside to provide the missing support in Squeak. Then methods (& classes) can be moved from there into Squeak when we see fit.</div></blockquote> <br></div><div>Thanks</div><div><br></div><div>I started by adding the protocol 'Squeak compatibility' to the CPlatformConfig class and then putting squeakDoFoo in there when doFoo is incompatible with Squeak. </div><div>However, your approach is the one to take. It neither forks nor clutters the existing pharo CMakeVMMaker package.</div><div><br></div><div><br></div><div>Mini-refactoring #1 here we go!</div><div><br></div><div><br></div><div><br></div><div>Cordially,</div><div><br></div><div><br></div><div>tty</div><div><br></div><div><br></div><br></div></body></html>