I was thinking about the config issue and thought of something that might make everyone unhappy (aka a possible compromise). How about adding: 'configs_with_source 'configs_with_source none or something similar? This would restrict the keyword pollution to domains in which users may want to have configs and source in the same file. If that is reasonable we can argue about the default separately... :-) Not necessarily the cleanest solution, but much easier to handle in terms of supporting existing flows. Gord. -- -------------------------------------------------------------------- Gordon Vreugdenhil, Staff Engineer 503-685-0808 Model Technology (Mentor Graphics) gordonv@model.comReceived on Sat Apr 23 13:28:47 2005
This archive was generated by hypermail 2.1.8 : Sat Apr 23 2005 - 13:30:58 PDT