octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #29475] new incompatibility of MEX function in


From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #29475] new incompatibility of MEX function in Octave 3.2.x
Date: Fri, 09 Apr 2010 18:09:41 +0000
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100308 Iceweasel/3.5.8 (like Firefox/3.5.8)

Update of bug #29475 (project octave):

                  Status:               Need Info => Fixed                  
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #7:

OK, I checked in my change.

"Yes, I modify mxArray only for full matrices and arrays of types char,
integer, and real numbers."

The point Jaroslav and I are trying to make is that you can still expect to
have trouble with your assumptions if someone passes a range or a diagonal
matrix or a permutation matrix instead of an actual full matrix object because
ranges and diagonal matrices and permutation matrices are special data types
in Octave that do not have the same representation as a full matrix, so it is
not possible to directly access the data to them in the same way as in Matlab.
 So Octave creates a full matrix from these special types first, then gives
you a pointer to that data.  So in those cases, there is no way for you do to
what you are trying to do (modify in place the argument to a MEX function).


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?29475>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/





reply via email to

[Prev in Thread] Current Thread [Next in Thread]