<br><br><div class="gmail_quote">On Tue, Mar 8, 2011 at 12:00 AM, Mariano Martinez Peck <span dir="ltr"><<a href="mailto:marianopeck@gmail.com">marianopeck@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>Hi guys. I notice that most of the times, the usage of #isIntegerObject: is for checking whether the object is immediate or not, rather than if it is an Integer.<br>In addition, when we will have 64 bits, I guess we will encode more objects (small floats, dates, points, etc) than just integers...<br>
</blockquote><div><br></div><div>+1. When I add immediate characters I will do this. I also did this when I ported the Slang plugin system to VisualWorks in order to steal the WarpBlt plugin.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>So, what about renaming #isIntegerObjects: and friends to something like #isImmediateObject: ? I know that changing #isIntegerObject: or things like that is too heavy, but maybe we can start by deprecating it, or for the new code, to use #isImmediateObject: instead... so we start preparing ourselves for the future, in little steps.<br>
</blockquote><div><br></div><div>I like isImmediate:.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>cheers<br><br>Mariano<br>
<br></blockquote></div><br>