Re: datestr bug in octaveforge

[Paul Kienzle]

I fixed datestr.m and updated the CVS.  Let me know if it fails for
you.

Paul Kienzle
address@hidden

On Thu, Jun 20, 2002 at 09:03:47AM -0600, E. Joshua Rigler wrote:
> Sorry, I'm not sure where to report bugs in octaveforge functions, so
> I'll cross-post...
> 
> There seems to be a simple, but recent, bug in the datestr.m (or
> datevec.m) function.  The datestr.m function parses output from
> datevec.m, and seems to expect the output to be a column vector, when,
> in the most recent version of octaveforge (2002.04.20, with 2.1.35
> base), datevec.m gives its output as a row vector.
> 
> One offending line in the datestr.m file is line 69:
> 
>   elseif (all(V(4:6,:)==0))
> 
> where V is the output from datevec.m.  I'll leave it to the octaveforge
> maintainers to determine whether datevec or datestr needs to be fixed.
> 
> -EJR
> 
> 
> 
> -------------------------------------------------------------
> 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
> -------------------------------------------------------------
> 



-------------------------------------------------------------
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
-------------------------------------------------------------