Code Control with IDL [message #1709] |
Fri, 25 February 1994 12:58 |
sylvain
Messages: 2 Registered: September 1993
|
Junior Member |
|
|
We are developping a reduction package that runs under IDL. We are trying to
ensure code control in the reduction, namely we want to make sure that each
routine used by the reduction proccess has the correct SCCS id (all our
routines are registered under SCCS).
Currently we implementing this by restricting the IDL's !path to '' (hence
) and by executing a cd to the directory that holds the correct registered
version of the reduction s/w. Unfortunatly this can be very easily defeated by
at least a couple of obvious way:
- executing a CD from within IDL (hence changing the location of '.')
- executing a .run /some/where/that.pro to overwrite the procedure in
./that.pro
- changing the value of !PATH, etc...
You can compile a dummy 'cd.pro' function, but the intrinsic CD will be
executed (eventhough help will list you CD as a compiled function :), and I
don't know of any way to disable the executive command ".RUN". Of course, I'd
love to see IDL stop looking in '.' first (how hard is it to add !path =
".:"+!path in your startup file ?).
Anyway, I would be surprised if we were the first to encounter this problem.
Has anybody out there tried to garantee code control in IDL?
Thanks,
Sylvain G. Korzennik
--
"Nequaquam vacuum"
Harvard-Smithsonian Center for Astrophysics
Solar and Stellar Physics Division. Mail Stop 16.
60 Garden Street, Cambridge, MA 02138.
(617) 495-7451, FTS 830-7451, FAX (617) 495-7049
(sylvain@cfassp.harvard.edu Internet/Arpanet)
or
(sylvain@cfa.harvard.edu Internet/Arpanet)
(cfa::sylvain SPAN/DECnet)
(sylvain@cfa Bitnet/Earn)
(skorzennik SolarMail)
|
|
|