Experimental Physics and
Industrial Control System

All,

It appears that, both on Unix and Windows, the header files have their
permissions set to writeable after being installed into the include
directories. When I am in the IDE working away I sometimes inadvertently
double click on a compiler error message and end up
auto-opening-for-editing, and eventually modifying, an installed include
file. It can definitely be very confusing if one modifies the installed
include file, and not the source for the installed include file. I try to
keep my guard up against this issue, but seem to keep repeating the same
mistake.

So, given this perspective and some others, it appears to be sensible for
all include files to have their permissions set to un-writable when they are
installed, but maybe there is some practical issue that prevents this from
being standard behavior that I don?t see? 

Your thoughts?

Jeff
______________________________________________________
Jeffrey O. Hill           Email        [email protected]
LANL MS H820              Voice        505 665 1831
Los Alamos NM 87545 USA   FAX          505 665 5107

Message content: TSPA

Replies:

Re: why doesnt the include file install set the file permisions to unwritable? Eric Norum

Navigate by Date:

Prev: RE: sscan, asyn and mutexes [SEC=UNCLASSIFIED] LYNCH, Damien

Next: RE: why doesnt the include file install set the file permisions to unwritable? Jeff Hill

Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <2009>  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 

Navigate by Thread:

Prev: RE: sscan, asyn and mutexes [SEC=UNCLASSIFIED] LYNCH, Damien

Next: RE: why doesnt the include file install set the file permisions to unwritable? Jeff Hill

Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <2009>  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024