<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-text-flowed" style="font-family: -moz-fixed;
font-size: 12px;" lang="x-unicode">On 1/30/21 6:50 PM, Joerg
wrote:
<br>
> Now, do I understand you correctly that while writing the rsc
file you want
<br>
> to compress consecutive 0X to only one 0X? Do you really want
to compress
<br>
> the string area while writing to (huge) disk, where normally
space is no
<br>
> issue?
<br>
<br>
No. To repeat: I'm talking about CPU instructions and memory
reads--i.e.
<br>
trying to measure this "optimization" on the terms that were
presumably a
<br>
concern at the time the strategy was chosen--not an attempt to
optimize for
<br>
disk space.
<br>
<br>
> To optimize the File IO you would turn this [...] into
something like this
<br>
<br>
I'm not sure where that sample comes from. It doesn't match the
code in the
<br>
module loader (and it wouldn't make sense; the module loader is
doing a file
<br>
read, not a write).
<br>
<br>
> As strings are written byte by byte, the possibly different
endianesses of
<br>
> the reading and writing systems do not matter.
<br>
<br>
Right, this reinforces what I'm referring to. When dealing with
strings,
<br>
operations are going to occur on a character-by-character, anyway,
due to
<br>
external constraints involving the nature of strings--as in the
section of the
<br>
module loader that I linked to, and as you're describing now. So
again: in
<br>
concrete terms, where does the efficiency for word alignment come
in? In
<br>
trying to reason about the strategy, I've <span
class="moz-txt-underscore"><span class="moz-txt-tag">_</span>only<span
class="moz-txt-tag">_</span></span> found downsides so far.
<br>
<br>
<div class="moz-txt-sig"><span class="moz-txt-tag">-- <br>
</span>Colby Russell
<br>
</div>
</div>
</body>
</html>