Re: Re: instrument-control / MATLAB compatibility

[Markus Bergholz]

On Wed, Jul 17, 2013 at 2:26 PM, Stefan Mahr <address@hidden> wrote:

> > I'm about to work on octave instrument-control to improve compatibility to MATLABs instrument control. For 'fprintf' the online doc is not very helpful. However, the behaviour of instrument-controls 'fprintf' seems different compared to standard 'fprintf':
> >
> >   fprintf(obj,'format','cmd','mode')
> >
> >   'format' can be a format specifier like %s, %c, or %d.
> >   'cmd' is expected as a string.
> >
> > If 'cmd' is a string, a format specifier like '%d' doesn't make sense. Could someone test if 'cmd' could be a array of type 'double' too?
> >
> >   fprintf(obj, '%d', [1 2 3 4])
> >
> > Thanks. Other hints are also welcome.
> >
> > Stefan
> > _______________________________________________
> > Help-octave mailing list
> > address@hidden
> > https://mailman.cae.wisc.edu/listinfo/help-octave
>
> Let me check that I got it right. You want that somebody tests in MATLAB, right?
>

Yes, correct.

We've figured this out on #octave-de

The result for fprintf(t,'%d',[1 2 3 4]);  was

>> fscanf(t)  
Warning: Unsuccessful read: A timeout occurred before the Terminator was reached. 

ans =

1234

 

_______________________________________________
Help-octave mailing list
address@hidden
https://mailman.cae.wisc.edu/listinfo/help-octave

--
icq: 167498924
XMPP|Jabber: address@hidden