login
Header Space

 
 

Re: shared libs - can everyone be happy with this?

Score:
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
Date: Monday, August 17, 1992 - 11:22 am

In article <d-dyhz_@rpi.edu> maniattb@cs.rpi.edu (Bill Maniatty) writes:

Hopefully we won't start another nasty chain here.. but someone correct
me if I'm wrong, but I've always been from the school that said that
all static variables went into the code space, otherwise how would
they be loaded in.  If one cannot modify the code space then I would
see it as impossible to modify a static variable.   In effect when you
declare something static and you modify it, haven't you modified your
code?   If we lost this ability, then I would see it as quite tricky
to implement static declarations with some elaborate loader that would
have to be implemented.  As it stands, design is simplified, and there
is no sacrifice in execution speed.   If a programmer wants to modify
his code or store values within the code, we should let him.   There's
only one reason to protect that, and it's to protect the programmer from
himself or herself.   Any programmer that intentionally modifies something
in code space will most probably know what is going on.  As to integrity
issues, if you make it to break, it's your fault.

Yeah, it's not the best view, but it's the way I see things.   I don't
want to start any long debates on the issue, so if you disagree with me,
reply by email.  "Oh I love mail" - The Count, Sesame Street.
--
Nathan I. Laredo (this spot: $9) Internet: gt7080a@prism.gatech.edu 
uucp:  ...!{decvax,hplabs,ncar,purdue,rutgers}!gatech!prism!gt7080a
"Having had the correct view is nothing meritorious: statistically,
 it is almost inevitable..."  -- Mr. Palomar,  On biting the tongue
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: shared libs - can everyone be happy with this?, Nathan I. Laredo, (Mon Aug 17, 11:22 am)
speck-geostationary