|
From: | Rik |
Subject: | [Octave-bug-tracker] [bug #35157] Naive users baffled by "complex scalar type invalid as index value" |
Date: | Fri, 23 Dec 2011 20:31:36 +0000 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0 |
Follow-up Comment #13, bug #35157 (project octave): One thing to remember is that it is the typeinfo of the index expression which is being checked, not the actual characters 'i' or 'e'. For example: a = [1:3]; idx = i; a(idx) error: complex scalar type invalid as index value I agree with Jordi that it is useful to know why the index expression is failing. In some cases the expression may be very complex (pun intended) and it would be useful in debugging to have this extra information. As for the problem with 'doc XXX', I fixed that in this changeset on the stable branch (http://hg.savannah.gnu.org/hgweb/octave/rev/8a2dc08886ea) _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?35157> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |