<div dir="ltr">Yes, I have to go back and re-introduce something that lets us build a non-arc version for 32bit, and a arc aware version for os-x 64bit, an iOS 32/64bit</div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Sep 27, 2015 at 1:19 AM, Colin Putney <span dir="ltr"><<a href="mailto:colin@wiresong.com" target="_blank">colin@wiresong.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Sep 27, 2015 at 1:02 AM, <span dir="ltr"><<a href="mailto:johnmci@smalltalkconsulting.com" target="_blank">johnmci@smalltalkconsulting.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br><div dir="auto"><div>99.5% is the code I wrote a number of years back. Earlier this year I took the Pharo code, code from minor squeak updates and code from Pyonkee to consolidate and convert into an ARC aware base. This makes iOS and 64bit OS X base happy, the legacy 32bit obj-c kernel not so much.</div><div><br></div><div>Now I have to backport the code to a format that works in both environments. </div></div></blockquote><div><br></div><div>IIUC, that means the Pharo VM is *not* ARC-aware, which is why it doesn't leak memory. What you've posted now is a step forward from all that, but not yet complete. Is that right?</div><div><br></div><div>-Colin </div></div></div></div>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr">===========================================================================<br>John M. McIntosh. Corporate Smalltalk Consulting Ltd <a href="https://www.linkedin.com/in/smalltalk" target="_blank">https://www.linkedin.com/in/smalltalk</a><br>===========================================================================<br></div></div></div></div>
</div>