| 1 |
Uncompiled code is not loaded into ram because it is only text. The |
| 2 |
exception is when you are editing it..! Unless I've been compiling all |
| 3 |
these years for no reason...:) Code must actually be compiled into a |
| 4 |
binary and called in one way or another to be loaded into ram. |
| 5 |
|
| 6 |
If you mean compiled, unused code can be loaded into ram, that is |
| 7 |
correct, but there is nothing the user can do about that - it's a |
| 8 |
function of the application: not all compiled code gets ran at a given |
| 9 |
time, because perhaps not all functions are being utilized at any given |
| 10 |
moment - depends on the program. |
| 11 |
|
| 12 |
On 01/22/06 03:47:12, Kristian Poul Herkild wrote: |
| 13 |
> Paul S. Bains wrote: |
| 14 |
>> You are not being dense - unused code does nothing but take up disc |
| 15 |
>> space. |
| 16 |
> |
| 17 |
> Well, the code _can_ be loaded, without being executed, and therefore |
| 18 |
> taking up RAM. |
| 19 |
> |
| 20 |
> -Kristian Poul Herkild |
| 21 |
>-- |
| 22 |
> gentoo-user@g.o mailing list |
| 23 |
> |
| 24 |
-- |
| 25 |
There are 10 kinds of people in the world: those who understand binary, |
| 26 |
and those who don't. |
| 27 |
|
| 28 |
-- |
| 29 |
gentoo-user@g.o mailing list |
Archives