<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br>Pointer to struct seems like the most obvious choice. </div><div><br>- Bert -<div><br></div></div><div><br>On 06.04.2013, at 17:15, Eliot Miranda <<a href="mailto:eliot.miranda@gmail.com">eliot.miranda@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><span></span></div></blockquote><blockquote type="cite"><div><br><br><div class="gmail_quote">On Thu, Apr 4, 2013 at 5:19 PM, David T. Lewis <span dir="ltr"><<a href="mailto:lewis@mail.msen.com" target="_blank">lewis@mail.msen.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
On Thu, Apr 04, 2013 at 01:25:10PM -0700, Eliot Miranda wrote:<br>
><br>
> On Thu, Apr 4, 2013 at 3:17 AM, Nicolas Cellier <<br>
> <a href="mailto:nicolas.cellier.aka.nice@gmail.com">nicolas.cellier.aka.nice@gmail.com</a>> wrote:<br>
><br>
> ><br>
> > Yes, I always wanted to ask what oops signed-ness was good for?<br>
> > IMO, they could simply be declared usqInt.<br>
> ><br>
><br>
> +10 raisedTo: SmallInteger maxVal. But the milk is already spilt :)<br>
><br>
> I'm glad you said that. I'm reminded of House of Cards. "You might think<br>
> so but I couldn't possibly comment." ;)<br>
><br>
> It might be worth-while trying to make this change and fixing the very few<br>
> places where signedness is important (the SmalInteger arithmetic<br>
> primitives).<br>
><br>
<br>
</div>IMO an object pointer should be declared sqOop to clearly distinguish<br>
it from some something that is intended to be used as an integer. </blockquote><div><br></div><div>OK, but is sqOop a void pointer or what? void pointers are ok except that they have to be cast all the time. char * is poor; too easily confused with other pointers. sqObj * (where sqObj is some opaque struct) is good. Integral types are easy to deal with. But signedness is the major thing to avoid. SO either unsigned or pointer. But which?</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">And<br>
a (32- or 64-bit) location in the object memory should have its own type<br>
declaration that would just coincidentally be the same size as a sqOop<br>
in the current implementations. And maybe there should be one more type<br>
definition to represent the 32-bit words in an indexable object.<br>
<br>
Dave<br>
<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>best,<div>Eliot</div>
</div></blockquote></body></html>