It is quite common for schematic capture software to have the concept of pin swap, could this be a path forward?
Otherwise I probably did not get what you are talking about. > Would it be a huge job to scan thru the module list, and recomp the ones > that do not have an enum based numbering scheme for their input pins? > > When I am carving up a new control function in hal, its somewhat of a > nuisance to stop and consult the man page for an and, or, xor, mul2, > mux2 or similar small module to find out if the first input is .in0 > or .in1. It would be a great help if a base number, 0 or 1, I don't have > a preference, was chosen and enforced for any new commits, but it should > be more consistent than it is now. > > I'll get me coat now. > > Cheers, Gene Heskett ------------------------------------------------------------------------------ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
