- From: Herman Bruyninckx <Herman.Bruyninckx_at_mech.kuleuven.ac.be>
- Date: Fri, 31 Jan 2003 15:56:01 +0100 (CET)
On Thu, 30 Jan 2003, David Schleef wrote: > > > Above you describe the behaviour of INSN_READ and INSN_WRITE. What you want > > > to be doing is using a INSN_CONFIG to modify the behaviour of commands. > > > > > Yes, but IMHO "modify the behaviour of commands" lead to nothing but > > chaos! A common structure such as Comedi is useful, but only where it > > can suggest a good common API for a whole range of DAQ cards and > > applications. This INSN_CONFIG thing to make an instruction "a la carte" > > is something I don't like too much... > > The alternative is not implementing it at all. At least with > extended-triggering configuration instructions, there's the > possibility to extend the interface for applications that just > don't fit the general model, and are too specific (to a particular > application or device) to change the general model to fit it. > yep, that's indeed the issue here: is what we would like to have sufficiently general in order to have in the Comedi API or not? And your the maintainer, so it's your call :-) We adapt to what you decide. And from what I read I tend to conclude that you think our stuff is not generic enough. So be it. We'll go the CONFIG way then. Herman -- K.U.Leuven, Mechanical Engineering, Robotics Research Group <http://people.mech.kuleuven.ac.be/~bruyninc> Tel: +32 16 322480
Received on 2003-01-31Z14:56:01