Re: low level I/O (GPIB, USBTMC, VXI11)

[Stefan Mahr]

Richard wrote:
> On 25/11/2012 11:25, c. wrote:
> > On 25 Nov 2012, at 10:21, Stefan Mahr wrote:
> >
> > > The instrument control package at octave forge creates a class as
> > > kind of file descriptor. While there are methods to access read,
> > > write, etc. from C++ / oct-File, there are no methods when using from
> > > octave.
> > >
> > > I know that classdef for .m file is not ready yet. Is it the same for
> > > .oct files?
> > I am not completely sure what you mean, is it something related to
> > these threads?
> >
> >
> > https://mailman.cae.wisc.edu/pipermail/help-octave/2012-November/054970.html
> >
> >
> > https://mailman.cae.wisc.edu/pipermail/octave-maintainers/2012-November/030767.html
> >
> >
> > https://mailman.cae.wisc.edu/pipermail/octave-maintainers/2012-November/030775.html
> >
> >
> > https://mailman.cae.wisc.edu/pipermail/octave-maintainers/2008-November/013305.html
> >
> > could you please explain a bit better?
> >
> > > Stefan
> > c.
>
> I suspect he wants to do something like this:
>
> http://www.mathworks.co.uk/matlabcentral/fileexchange/38964-example-matlab-class-wrapper-for-a-c++-class
>
> http://www.mathworks.com/matlabcentral/newsreader/view_thread/278243
>
> Richard

Example based an instrument control / serial:

  a=serial("/dev/ttyS0");
  srl_close(a);

Matlab has a second way to call a method:

  a.close;  or   a.srl_close;

I don't know the actual state of octaves OOP, so my question is: Is the 
second way already supported by octave? If yes, what's wrong with the 
.oct file? Also, I would expect the list of the methods by calling

  methods("octave_serial")


Stefan