On Fri, Nov 29, 2013 at 05:27:17PM -0700, Sebastian Kuzminsky wrote:
> 
> I think a #include-like directive would be both useful and easy to 
> implement, but i'm not volunteering to do it.  ;-)

I think this might be barking up the wrong tree: a tree that only
you and your fellow programmers can see.

I gently suggest considering whether concentrating on our
configurators like stepconf might be better in the long run for
fixing the root problem: that configuring is intricate and hard for
the new user.  [actually I'm not sure what "root problem" Charles is
trying to solve so I am guessing here -- something stepconf doesn't
currently handle perhaps?]

This line of thought fits in with Todo-2.6 items in section 8,
especially 8.2.: remove [sample configs] that can be easily
regenerated by stepconf.

Paradoxically, the more intricate you make the ini and hal languages
with the goal of "ease of use", the harder it is for the gui
programs to handle (especially read and rewrite) them, the more
brittle those programs get, and the less likely we are to want to
maintain or improve them -- in effect, hurting *real* "ease of use"
more than helping.  In particular I'm thinking of the crazy things
the PID-tuning gui program has to go through because of how the hal
file can refer to variables in the ini file.  My unverified
institutional memory tells me this feature was the cause of at least
one regression released to users.  If you add includes, that program
has to get more twisted still, or more likely, it would just remain
broken for this new kind of config.

My 2 cents only.

Chris

------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to