On 6 November 2013 06:27, Michael Haberler <[email protected]> wrote: > - on startup, rather than using the hal Python comp to connect directly to > HAL, collect all pin names, types and direction, and pass this list to an > HALrcomp API class instance; this would be the basis for the initial bind > operation
Rather than explicitly add new pins, would it be practical to change the function of the "net" command to provisionally create/register any pins that don't exist when it is called? The obvious problem with this is that simple typos in pin names will not be picked up on the first pass, but then I suppose there is a similar problem with the newpin command. I don't know how you would test for whether a pin was "real" or "typo". It is perfectly reasonable to create pins and not connect to them, most of the HAL components do that all the time. Nor is it unusual to create a net and signal and not have any "writer" in the net. (Many of the sample configs do this) -- atp If you can't fix it, you don't own it. http://www.ifixit.com/Manifesto ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
