| From: | "Robert A. Hayden" <hayden@*******.MANKATO.MSUS.EDU> |
|---|---|
| Subject: | Compilers/Languages |
| Date: | Tue, 20 Jul 1993 20:33:06 -0500 |
of Game Balance{tm}, it is probably a problem.
A good compiler is going to generate code that is 'tight'. This means it
does the most it can with as little code/size as possible.
The better the compiler, the tighter the code. Of course, compiling this
code with a different compiler will take longer, but the resultant program
will be smaller, faster, and more efficient.
-----
*ding* <-- That's a thought
DEPENDENT PROGRAMS
What if you designed a program to share code strings with another program?
That is, there are portions of code that are identical between two
programs, so you share these identical portions, thus reducing overall size.
For example, let's say you had a 100mp Analyze and a 200mp attack/poison.
Obviously, the attack program must have some type of analyzing sequence in
order to make the attact effective. So you design a dependent package.
the 100mp Analyze and 200mp attack/poison is compiled together into one
program that might only be 240mp in size total, because the redundant code
has been eliminated. Of course, to use either of the programs, the entire
combo program must be loaded.
-------
Comments? It would work, just not sure about the rules for it.
{[> Robert A. Hayden ____ hayden@*******.mankato.msus.edu <]}
{[> \ /__ hayden@****.cs.mankato.msus.edu <]}
{[> \/ / aq650@****.INS.CWRU.Edu <]}
{[> #include <std_disclaimer.h> \/ <]}
-=-=-
GEEK CODE v1.0.1: GSS d- -p+(---) c++(++++) l++ u++ e+/* m++(*)@ s-/++
n-(---) h+(*) f+ g+ w++ t++ r++ y+(*)
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Random Thought:
"Once they go up, who cares where they come down? That's not my department."
-- Werner von Braun
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
