On Wednesday 26 October 2005 04:37 pm, Marek Wodzinski wrote: > On Wed, 26 Oct 2005, Alfille, Paul H.,M.D. wrote: > > Ahhh... I'm sorta a software guy. 1=on 0=off > > Sorry for all the confusion. > > I'm a hardware based software guy:-) > > > The easiest way to bypass this is the add an "alias" -- another property > > that is the inverted state of the PIO pin. What should it be called? > > Maybe another idea: something like --dont-convert, --dont-negate or > --raw-rw to configure? > > And do not convert input/output with this option - just raw values like in > documentation of chips. > > regards > > majek
Umm... unmanageable. We can't have incompatible behavior based on compilation settings, the confusion would be prodigious. A little more acceptable would be command line options -- though when you start negotiating between server and client settings, and owperl... it gets complex again. How about rPIO? It stands for "raw PIO" or "real PIO" or "reversed PIO"? The name reveals the syntax. Just looking at the man page brings the issue to light. Paul ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
