<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto;"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div class="im"><div><br></div></div>Absolutely no idea.<br><div><div>BitBlt is rich enough (color maps or direct
color components, depths, endianness) to make this unpredictable by
simply analyzing sender chain in source code (it's too deep and
convoluted).<br></div><div>The best way is to try it, but then one must
choose a benchmark, and here again it is a difficult decision, because
maybe you didn't bench a path that some other use intensively, how to
guess without above analysis?<br><br></div><div>I saw those un-necessary mismatch while analyzing Graphics code...<br></div><div>By a principle of economy, I suggest to remove them.<br></div><div>Simplifying code a little bit is already a win.<br>
<br></div></div></div></div></div></blockquote><div>BTW, did you see that scaled rgb components use 10bits while scaled alpha uses 8?<br></div></div></div></div></blockquote><div><br></div>No :) because I’m totally ignorant of this part and I need time to learn and I’m too busy and too sick because I work too much.</div><div><br></div><div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>This was in Squeak already and has been perpetuated in Pharo refactoring...</div></div></div></div></blockquote></div></body></html>