From: | Dave Sherohman <esper@*****.IMA.UMN.EDU> |
---|---|
Subject: | STRIPpers |
Date: | Tue, 20 Jul 1993 23:45:18 -0500 |
have an additional restriction to impose - based upon your rationale for the
program's existence and workings, it would seem to me that a Strip program
would have to be custom-coded for the MPCP it was to run on (for pretty
much the same reasons as why the code becomes non-portable). Also, I think
it would be reasonable to allow for the use of a Strip with a lower rating
than the MPCP, but then the reduction is 5% * Strip Rating instead of
5% * MPCP Rating. (Coupled with MPCP-specific Strips, this would basically
just mean that you can throw together a basic Strip to improve your memory-
efficiency a little until you can finish the full-rated Strip for full
optimization.) Naturally, post-Strip size would be based solely off the
program's original (un-Stripped) size - no running Strip-6 over the same
program twice to get a 51% reduction; though you could run a Strip-1
without hampering a future Strip-5.
esper@***.umn.edu