Re: COMEDI wrapper (was: Re: Data acquisition in Octave)

[Olaf Till]

On Fri, Nov 21, 2008 at 12:08:28PM +0100, Olaf Till wrote:
> - comedi_calibration_t
> 
> one instance (necessary) per device, allocated and freed with
> comedilib functions, independently of comedi_t structure; user can
> create arbitrarily many (equal) instances --- so it should
> automatically be freed if an Octave user variable containing it gets
> overwritten or out of scope, or if the user clears it; probably you
> have means to do this in Octave ...
> 
> - some allocations for filling in the comedi_cmd and comedi_insn
>   structures
> 
> similar problem as the last
>
Regarding the last point: maybe these structures should not be wrapped
into an octave_value, since the user must configure them (so either a
couple of function for configuration would be needed, or a
representation of these structures in regular Octave cells/structures
defined). Maybe these structures should _only_ be represented as
Octave cells/structures and the corresponding comedi structures be
generated on the fly by comedi_cmd() et al.