On 10/16/2011 06:07 PM, Kent A. Reed wrote: > Your comment about hal files possibly being hierarchical or sequential > is spot on. Handling multiple .hal files would be a trivial extension of > my current script (love that Python!). When I first wrote down what I > thought would be a useful set of program options, one option was to > accept an .ini file as the defining entity and let it pull in all > relevant .hal files (handling variable substitution of course). I > haven't gotten around to it. To be honest, once I started extracting > configurations from running EMC2 I didn't feel the need since EMC2 has > already done the work for me.
Kent, thank you for the effort to put this together. I'm sure it will be very useful. Using EMC2's output as a predictable and syntactically consistent input seems like a good expedient. <fantasy_mode> An extension, which is probably a fair amount of work, might be to make diagram annotations from the hal files. It could import the hal files directly and parse them for comments of a predefined form. Such comments could wind up as text in a place on the diagram, netlist-wise near to where they were found on the hal file. </fantasy_mode> Karl ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
