<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoPlainText>+1<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><i>Word</i> can be vague. Even a <i>byte</i> can be 7-bits in some odd cases. Counting bits is clearest and most reliable. We all still agree on how big a bit is.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-----Original Message-----<br>From: Cuis-dev [mailto:cuis-dev-bounces@lists.cuis.st] On Behalf Of john pfersich via Cuis-dev<br>Sent: Monday, May 27, 2019 00:33<br>To: Discussion of Cuis Smalltalk <cuis-dev@lists.cuis.st><br>Cc: john pfersich <jpfersich@gmail.com><br>Subject: Re: [Cuis-dev] [Integrated] Should we rename these? Re: support for variable indexable subclasses of 8/16/32/64 bits</p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>+1<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>/*—————————————————-*/<o:p></o:p></p><p class=MsoPlainText>Sent from my iPhone<o:p></o:p></p><p class=MsoPlainText><a href="https://boincstats.com/signature/-1/user/51616339056/sig.png"><span style='color:windowtext;text-decoration:none'>https://boincstats.com/signature/-1/user/51616339056/sig.png</span></a><o:p></o:p></p><p class=MsoPlainText>See <a href="https://objectnets.net"><span style='color:windowtext;text-decoration:none'>https://objectnets.net</span></a> and <a href="https://objectnets.org"><span style='color:windowtext;text-decoration:none'>https://objectnets.org</span></a><o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>> On May 26, 2019, at 22:27, Andres Valloud via Cuis-dev <<a href="mailto:cuis-dev@lists.cuis.st"><span style='color:windowtext;text-decoration:none'>cuis-dev@lists.cuis.st</span></a>> wrote:<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Why should accessing bytes differently need copying the bytes into a different class? The bytes won't change, no?<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> VW has a useful abstraction for this, the class UninterpretedBytes. While at first similar to a regular ByteArray, UninterpretedBytes implements things like shortAt:, doubleAt:put: and so on. Now you need just one class instead of n.<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> If those selectors could be named after standard types of fixed length too (like 'uintptr_t'), then great because e.g. nobody says what the size of a C 'long' is.<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>>> On 5/26/19 13:49, Juan Vuletich via Cuis-dev wrote:<o:p></o:p></p><p class=MsoPlainText>>> Folks, these names are getting confusing. I think we'd name them better. What about ByteArray, SignedByteArray, Int16Array, SignedInt16Array, Int32Array, SignedInt32Array, Int64Array, SignedInt64Array, Float32Array, Double64Array, SignedPoint16Array and SignedPoint32Array?<o:p></o:p></p><p class=MsoPlainText>> -- <o:p></o:p></p><p class=MsoPlainText>> Cuis-dev mailing list<o:p></o:p></p><p class=MsoPlainText>> <a href="mailto:Cuis-dev@lists.cuis.st"><span style='color:windowtext;text-decoration:none'>Cuis-dev@lists.cuis.st</span></a><o:p></o:p></p><p class=MsoPlainText>> <a href="https://lists.cuis.st/mailman/listinfo/cuis-dev"><span style='color:windowtext;text-decoration:none'>https://lists.cuis.st/mailman/listinfo/cuis-dev</span></a><o:p></o:p></p><p class=MsoPlainText>-- <o:p></o:p></p><p class=MsoPlainText>Cuis-dev mailing list<o:p></o:p></p><p class=MsoPlainText><a href="mailto:Cuis-dev@lists.cuis.st"><span style='color:windowtext;text-decoration:none'>Cuis-dev@lists.cuis.st</span></a><o:p></o:p></p><p class=MsoPlainText><a href="https://lists.cuis.st/mailman/listinfo/cuis-dev"><span style='color:windowtext;text-decoration:none'>https://lists.cuis.st/mailman/listinfo/cuis-dev</span></a><o:p></o:p></p></div></body></html>