William Chops Westfield wrote:
> This has its advantages, but one of the "problems" with windows (that
> tends
> to be less prevalent on unix) is the use of system-wide directories for
> configuration info that SHOULD be created on a per-user basis.  Most of
> the microcontroller tools we're talking about should count as
> "individual
> use" programs for the most part, and really ought to have config info
> stored in the per-user area (perhaps in addition to system-wide
> configs.)

Actually my software supports this too.  The root environment file
(GLOBAL.ENV) defines a search path for environment files.  At startup the
root environment file is processed iteratively, each time taking into
account the search path produced by the last path.  The default GLOBAL.ENV
contains path entries for the site, node, and user.  These don't have to
exist of course, but the mechanism is there for creating custom environment
files that override the defaults in the global ENV directory.  Most
environment files are structured in such a way that the specific files need
only contain the incremental customizations, with the ones in the standard
ENV directory acting as defaults.


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist