| 1 |
Perhaps I misunderstood the poster - unused, uncompiled code cannot be |
| 2 |
loaded into RAM, unless you editing it. Unused compiled code can, but |
| 3 |
that is beyond the realm of the user. If the developer has functions |
| 4 |
that are not ever being used, then that's the developer's fault. |
| 5 |
|
| 6 |
On 01/22/06 03:55:00, Alexander Skwar wrote: |
| 7 |
> Paul S. Bains wrote: |
| 8 |
> |
| 9 |
> > You are not being dense - unused code does nothing but take up disc |
| 10 |
> |
| 11 |
> > space. |
| 12 |
> |
| 13 |
> That's not correct. It offers the potential of being |
| 14 |
> executed and thus, it offers the potential of being |
| 15 |
> a security threat. Thus it is better to NOT have the |
| 16 |
> code around at all. |
| 17 |
> |
| 18 |
> Alexander Skwar |
| 19 |
> -- |
| 20 |
> You see but you do not observe. |
| 21 |
> Sir Arthur Conan Doyle, in "The Memoirs of Sherlock Holmes" |
| 22 |
> -- |
| 23 |
> gentoo-user@g.o mailing list |
| 24 |
> |
| 25 |
> |
| 26 |
> |
| 27 |
|
| 28 |
-- |
| 29 |
There are 10 kinds of people in the world: those who understand binary, |
| 30 |
and those who don't. |
| 31 |
|
| 32 |
-- |
| 33 |
gentoo-user@g.o mailing list |
Archives