[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #35157] Naive users baffled by "complex scalar
From: |
Jordi Gutiérrez Hermoso |
Subject: |
[Octave-bug-tracker] [bug #35157] Naive users baffled by "complex scalar type invalid as index value" |
Date: |
Fri, 23 Dec 2011 17:36:55 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20110109 Jungledinosaur/3.6.13 |
Follow-up Comment #9, bug #35157 (project octave):
I don't see a reason to not provide a more specific error message if it's
something that is already being checked for.
Also, given the frequency with which i and j are chosen as index variable, I
think a(i) is provoking an error far more frequently than a(e) is.
Furthermore, the reason you don't see i and j as variables is because by
default they're not. They're in fact functions, and when you do i = 1, you're
shadowing function. You can do i(2,5) with i's default value, for example, to
get a matrix full of i.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?35157>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #35157] Naive users baffled by "complex scalar type invalid as index value", Clem, 2011/12/22
- [Octave-bug-tracker] [bug #35157] Naive users baffled by "complex scalar type invalid as index value", Jordi Gutiérrez Hermoso, 2011/12/23
- [Octave-bug-tracker] [bug #35157] Naive users baffled by "complex scalar type invalid as index value", Jordi Gutiérrez Hermoso, 2011/12/23
- [Octave-bug-tracker] [bug #35157] Naive users baffled by "complex scalar type invalid as index value", Clem, 2011/12/23
- [Octave-bug-tracker] [bug #35157] Naive users baffled by "complex scalar type invalid as index value", Jordi Gutiérrez Hermoso, 2011/12/23
- [Octave-bug-tracker] [bug #35157] Naive users baffled by "complex scalar type invalid as index value", Michael Godfrey, 2011/12/23
- [Octave-bug-tracker] [bug #35157] Naive users baffled by "complex scalar type invalid as index value", Michael Godfrey, 2011/12/23
- [Octave-bug-tracker] [bug #35157] Naive users baffled by "complex scalar type invalid as index value", Jordi Gutiérrez Hermoso, 2011/12/23
- [Octave-bug-tracker] [bug #35157] Naive users baffled by "complex scalar type invalid as index value", Michael Godfrey, 2011/12/23
- [Octave-bug-tracker] [bug #35157] Naive users baffled by "complex scalar type invalid as index value",
Jordi Gutiérrez Hermoso <=
- [Octave-bug-tracker] [bug #35157] Naive users baffled by "complex scalar type invalid as index value", Michael Godfrey, 2011/12/23
- [Octave-bug-tracker] [bug #35157] Naive users baffled by "complex scalar type invalid as index value", Michael Godfrey, 2011/12/23
- [Octave-bug-tracker] [bug #35157] Naive users baffled by "complex scalar type invalid as index value", Michael Godfrey, 2011/12/23
- [Octave-bug-tracker] [bug #35157] Naive users baffled by "complex scalar type invalid as index value", Rik, 2011/12/23
- [Octave-bug-tracker] [bug #35157] Naive users baffled by "complex scalar type invalid as index value", Clem, 2011/12/23
- [Octave-bug-tracker] [bug #35157] Naive users baffled by "complex scalar type invalid as index value", Muhali, 2011/12/27
- [Octave-bug-tracker] [bug #35157] Naive users baffled by "complex scalar type invalid as index value", Jordi Gutiérrez Hermoso, 2011/12/29
- [Octave-bug-tracker] [bug #35157] Naive users baffled by "complex scalar type invalid as index value", Rik, 2011/12/30