More possible incompatibilities in Yalmip?

[John W. Eaton]

On 29-Nov-2011, fork wrote:

| Here is another question, before I go clobber the source code.  
| 
| There is an snippet in the basic test program like this:
| 
| detected = which('yalmip.m','-all');
| if length(detected)>1
|     disp('blah blah blah ...');
|     detected
|     return
| end
| 
| In Octave, a string of 62 characters gets returned ("yalmip is a file, 
et...").
|  Is there any chance that ML returns a cell array or something?

https://savannah.gnu.org/bugs/?32088

Since you need it, maybe you can contribute the change for it?  :-)

| Also, there is another snippet "sdpvar x(1,1,'full','complex');" which I 
changed
| to "x = sdpvar(1,1,'full','complex');".  Is there any chance the original
| somehow works in ML?

I guess I'd have to see the function sdpvar.

I tried

  function foo (varargin) varargin, end
  foo x(1,1,'full','complex')

but Octave does not recognize the "x(1,1,'full','complex')" as a
(list of?) character string argument(s) to pass to foo as it would
with

  foo x y z

I don't know whether that works with Matlab.

jwe