The \"s{1}
annoyance\" of the title refers to the first line within the for-block below:
for s = some_cell_array
s = s{1}; % unpeel the enclosi
Just a small add-on to Sam Robert's comment to the original question, on why you should prefer s{:}
over s{1}
: easier bug tracking.
Imagine you mistakenly stored your cell s
as a column instead of a line. Then
for s = some_cell_array
will simply return a cell s
which is equal to some_cell_array
. Then the syntax s{1}
will return the first element of some_cell_array
, whereas s{:}
will produce a list of all elements in some_cell_array
. This second case will much more surely lead to an execution error in the following code. Whereas the first case could sometimes create a hard bug to detect.
I don't think there is a way to avoid this problem in the general case. But there is a way if your cell array has all numbers or all chars. You can convert to an array and let the for
loop iterate over that.
For example, this:
some_cell_array = {1,2,3}
for s = [some_cell_array{:}] % convert to array
s
end
Gives:
s =
1
s =
2
s =
3
Another option is to create a function that operates on every cell of the array. Then you can simply call cellfun and not have a loop at all.
I don't have any ideas about who would want this behavior or how it could be useful. My guess as to why it works this way, however, is that it's an implementation thing. This way the loop iterator doesn't change type on different iterations. It is a cell every time, even if the contents of that cell are different types.