[Top][All Lists]

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

Re: Help on error: can't perform indexing

From: Maynard Wright
Subject: Re: Help on error: can't perform indexing
Date: Wed, 14 Feb 2007 11:42:58 -0800
User-agent: KMail/1.9.1

I'm seeing a similar problem with the same error message.  I get the error 
message with two different Octave versions under Linux and a friend is able 
to reproduce exactly what I get under Windows. 

In my case, the Octave script file runs correctly and yields the right answer 
and the message is then displayed.  This occurs only when a script file with 
an extension ".m" is executed from within Octave.  When there is no extension 
or when the extension is other than ".m," the file cannot be executed without 
using source "filename."  When source is used to execute the file, I don't 
see the error message, even when the filename has a ".m" extension. 

When the ".m" file is executed as a script from the Linux command line, it 
works properly and the error message does not occur.

I used addpath() to add the path containing the file without effect.  The path 
was already in my bash shell PATH variable.

I was able to reproduce the problem with an empty script file, just to see 
whether it was something in my code.



On Wednesday 14 February 2007 08:05, Muthiah Annamalai wrote:
> On Wed, 2007-02-14 at 13:33 -0200, address@hidden wrote:
> > Dear Users,
> >
> > Runnning the code below, I got the error:
> >
> > octave.exe:35> prog.m
> > error: can't perform indexing operations for <unknown type> type
> Octave is not able to find the file prog in the PATH variable.
> Use function addpath() to add the directory where you have the file
> 'prog.m' to the PATH, then run prog.m
> OTOH, Octave tries to decode prog.m as a structure prog, with field m
> which is why it reports such an error I believe.
> ~ Muthiah
> _______________________________________________
> Help-octave mailing list
> address@hidden

reply via email to

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