On Sun, Apr 18, 2010 at 1:10 AM, Henrik Sperre Johansen <span dir="ltr">&lt;<a href="mailto:henrik.s.johansen@veloxit.no">henrik.s.johansen@veloxit.no</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">

<div class="im">�On 18.04.2010 01:05, Julian Fitzell wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Cool stuff, Nicolas. I&#39;m happy to see Grease getting use in the wild... I&#39;m curious to what degree it met your needs?<br>
<br>
I just recorded a podcast with James Robertson this week talking about cross-platform development. He asked what other projects were using Grease and I&#39;m afraid I didn&#39;t know to include yours. :)<br>
<br>
Julian<br>
</blockquote></div>
>From my limited experience, beyond the ANSI standard, Grease seems like a �step forward towards more dialect compatibility,<br>
2c: How about a &quot;Greasifier&quot; (Grease lubricate: ? ;) ), which would take as input a package/arbitrary unit of code, and emit an equivalent unit of code, in which methods whose �bytecodes would be equivalent to the dialect-specific Grease method were rewritten to use the Grease equivalent? (The other way around would ofc also be possible)<br>

</blockquote><div><br>Have you looked at Slime? It contains lint and rewrite rules for a bunch of non-portable Squeak code. The ones that have rewrite rules will allow you to replace it with valid Grease code. <br></div>
</div>
<br>It can&#39;t catch everything of course, but it&#39;s a start. Also, sadly, it&#39;s not currently portable because RB isn&#39;t the same on all platforms.<br><br>Julian<br>