Uncompiled code is not loaded into ram because it is only text. The
exception is when you are editing it..! Unless I've been compiling all
these years for no reason...:) Code must actually be compiled into a
binary and called in one way or another to be loaded into ram.
If you mean compiled, unused code can be loaded into ram, that is
correct, but there is nothing the user can do about that - it's a
function of the application: not all compiled code gets ran at a given
time, because perhaps not all functions are being utilized at any given
moment - depends on the program.
On 01/22/06 03:47:12, Kristian Poul Herkild wrote:
Paul S. Bains wrote:
You are not being dense - unused code does nothing but take up disc
space.
Well, the code _can_ be loaded, without being executed, and therefore
taking up RAM.
-Kristian Poul Herkild
--
gentoo-user@gentoo.org mailing list
--
There are 10 kinds of people in the world: those who understand binary,
and those who don't.
--
gentoo-user@gentoo.org mailing list
