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

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

[Octave-bug-tracker] [bug #40368] octave_config_info() should be read-on


From: Rik
Subject: [Octave-bug-tracker] [bug #40368] octave_config_info() should be read-only
Date: Fri, 25 Oct 2013 15:06:42 +0000
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0

Follow-up Comment #3, bug #40368 (project octave):

Is there a way Octave could produce a warning message in this situation? 
Trying to index into a non-existent variable with a string doesn't seem like
something that the user intended.

More samples


a("junk") = "abc"
error: A(I) = X: X must have the same size as I
a("junk") = "abcd"
a = adcb


The assignment succeeds when the index expression on the left matches the size
of the expression on the right.  And if you do an alphabetical sort on "junk"
the ordering is [1 4 3 2] so it appears that it is doing a = "abcd"([1 4 3
2]).


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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