Small footprint, what's that ?
-
Sometimes I saw some descriptions to certain 3rd party libraries use such term: "small footprint just 24K memory", or something the like. What is "footprint" ? And how to measure it ? Maxwell Chen People say "No news is good news". Then, no code is good code!?
-
Sometimes I saw some descriptions to certain 3rd party libraries use such term: "small footprint just 24K memory", or something the like. What is "footprint" ? And how to measure it ? Maxwell Chen People say "No news is good news". Then, no code is good code!?
A small 'footprint' refers to the amount of disk space and/or memory usage that the program uses, i.e. Internet Explorer has a large footprint because installing it takes up a lot of space, whereas something like Windows PowerToys has a small footprint because they use relatively little space and memory. As to measuring it, you can't really, it's a non-scientific term. HTH. -- Andrew.
-
A small 'footprint' refers to the amount of disk space and/or memory usage that the program uses, i.e. Internet Explorer has a large footprint because installing it takes up a lot of space, whereas something like Windows PowerToys has a small footprint because they use relatively little space and memory. As to measuring it, you can't really, it's a non-scientific term. HTH. -- Andrew.
Then, how did they make it? SQLite See the 4th note in section feature. Maxwell Chen People say "No news is good news". Then, no code is good code!?
-
Then, how did they make it? SQLite See the 4th note in section feature. Maxwell Chen People say "No news is good news". Then, no code is good code!?
Maxwell Chen wrote: Then, how did they make it? SQLite See the 4th note in section feature. That note says 20K "LINES" of C code which, of course, refers to the source code. It isn't the size of the binary or the memory usage of the component. -- Dana Holt Xenos Software
-
Then, how did they make it? SQLite See the 4th note in section feature. Maxwell Chen People say "No news is good news". Then, no code is good code!?
They've based their assumption upon the amount of source code in the project - i.e. less than 20,000 lines, which is not that big really, and might compile to less than a 400K executable. -- Andrew.
-
They've based their assumption upon the amount of source code in the project - i.e. less than 20,000 lines, which is not that big really, and might compile to less than a 400K executable. -- Andrew.
Andrew Peace wrote: less than 20,000 lines, which is not that big really, and might compile to less than a 400K executable. Then, why 20,000 lines compiles to 400,000 bytes executable? Maxwell Chen People say "No news is good news". Then, no code is good code!?
-
Andrew Peace wrote: less than 20,000 lines, which is not that big really, and might compile to less than a 400K executable. Then, why 20,000 lines compiles to 400,000 bytes executable? Maxwell Chen People say "No news is good news". Then, no code is good code!?
Well, it really depends on several factors: 1) whether speed or size optimisation was performed 2) whether there are many resources to be compiled as well (if you are included a lot of bitmaps in the binary you can get massive executables with hardly any code at all) 3) what other static libraries are linked with the executable. HTH, -- Andrew.
-
Andrew Peace wrote: less than 20,000 lines, which is not that big really, and might compile to less than a 400K executable. Then, why 20,000 lines compiles to 400,000 bytes executable? Maxwell Chen People say "No news is good news". Then, no code is good code!?
Maxwell Chen wrote: Then, why 20,000 lines compiles to 400,000 bytes executable? A single line of source code always results in more than one line of executable binary instruction code. Even a simple GOTO from BASIC translates into at least 5 bytes of executable - a JMP code, and 4 bytes of address. More complex functions can result in much larger blocks.