From: | The Deb Decker <RJR96326@****.UTULSA.EDU> |
---|---|
Subject: | Strip and languages |
Date: | Wed, 21 Jul 1993 15:55:58 -0500 |
of strips. What we're looking for is an optional way to give deckers detailed
choices about how they run their programs. If someone will examine all the
comments and write up a detailed post and explanation, maybe we could start
anew from a more solid mechanical/theoretical point.
My View: Commercial Programs are already compiled for something just short
of the maximum speed. Whether the decker decodes them or if they are availble
for different makes and models, the listed sizes and ratings should be the
standard. That way we don't have any sudden paradigm shifts in decking (short
of the Carter-Huth post).
Languages: A variety with different strengths and weaknesses. They could
specialize in areas of decking (combat, sensor) or application (math, text,
graphic imaging).
Strip: Used in conjunction with languages to make the final product smaller.
If you allow them to be used on commercial proframs, it should be more
difficult and/or you should get a smaller return, since (as I said above)
they are already well-optimized.
J Roberson