From bug-octave-request at bevo dot che dot wisc dot edu Mon Dec 18 22:24:58 2000 Subject: Small Documentation bug in 2.1.32 From: "John W. Eaton" To: Bill Lash cc: bug-octave at bevo dot che dot wisc dot edu Date: Mon, 18 Dec 2000 22:24:50 -0600 On 17-Dec-2000, Bill Lash wrote: | [My first attempt to send this seems to have gotten lost | along the way. Sorry if you get this twice] It was not automatically posted since you were not subscribed to the bug-octave list, and I hadn't forwarded it yet. | I finally got around to trying a more recent version of the | 2.1.xx family, and found that a .oct file I had written (for | 2.1.14) no longer compiled. I looked at oregonator.cc and | noticed that the line which used to read: | | ColumnVector x = args(0).vector_value (); | | now reads: | | ColumnVector x (args(0).vector_value ()); | | The file func.txi, however still includes the original | version. A patch for func.txi is included below. | | Now all I need to do is figure out exactly what this new | form is trying to say. My C++ is rusty from lack of | use. It's saying that vector_value now returns an Array object, which has no orientation, so you have to create a ColumnVector object using the ColumnVector constructor. You can also now use column_vector_value or row_vector_value methods to extract ColumnVector or RowVector objects, but then the Octave_value object must contain exactly what you ask for. Using vector_value allows the user of the function to pass either a row or column vector, and things will still work out fine. jwe ------------------------------------------------------------- Octave is freely available under the terms of the GNU GPL. Octave's home on the web: http://www.octave.org How to fund new projects: http://www.octave.org/funding.html Subscription information: http://www.octave.org/archive.html -------------------------------------------------------------