Re: wavread problems

[Keith Goodman]

Are you sure it is attempting the code? It should just be unwinding
the stack of functions that called the error line and at each one
printing out the line and column numbers.

I find it difficult, by the way, to visually unwind the error
messages. Would clever formatting help?

On 5/11/05, Robert A. Macy <address@hidden> wrote:
> Interestingly, on 2.1.50 binary the phrase...
> error("need two arguments");
> ...after an if() test DOES NOT return you from the
> function.  octave attempts the rest of the code.
> However,...
> error("need two arguments\n");
> ...does return you and the rest of the code is NOT
> attempted.
> 
>             - Robert -
> 
> On Wed, 11 May 2005 13:08:04 -0400
>  "John W. Eaton" <address@hidden> wrote:
> > On 11-May-2005, Doug Stewart wrote:
> >
> > BTW, you can write
> >
> >   error ("%s is not a WAV file", wavefile);
> >
> > instead of using sprintf because the error function
> > processes
> > arguments the same as printf.
> >
> > 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
> -------------------------------------------------------------
> 
>



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