Matlab Indexing Limitations
Why does Matlab support neither indexing of *function outputs* such as

    f()(1)

nor *stacked indexing* of variables such as 

    x(1)(2)

when Octave supports it? I'm guessing it is related to the complexity of optimizing complex code to make use of data parallelism. Having worked in imperative languages such as C/C++/Java and functional ones such Scheme/Lisp/Haskell I find this a *usability issue* as it *forces* (*teaches*) the programmer to *restrict* its thinking into writing in a *non-functional* style using *unneccesary temporary variables*. In turn this also becomes a *performance issue* as this syntactic limitation often leads to *costly reshape* operations in combination with non-intuitive code indexing statements.

So, Mathworks, if Octave can do it why can't you? You must have orders of magnitude more developers, right?

Matlab Indexing Limitations
===

Why does Matlab support neither indexing of *function outputs* such as

    f()(1)

nor *stacked indexing* of variables such as 

    x(1)(2)

when Octave supports it? I'm guessing it is related to the complexity of optimizing complex code to make use of data parallelism. Having worked in imperative languages such as C/C++/Java and functional ones such Scheme/Lisp/Haskell I find this a *usability issue* as it *forces* (*teaches*) the programmer to *restrict* its thinking into writing in a *non-functional* style using *unneccesary temporary variables*. In turn this also becomes a *performance issue* as this syntactic limitation often leads to *costly reshape* operations in combination with non-intuitive code indexing statements.

So, Mathworks, if Octave can do it why can't you? You must have orders of magnitude more developers, right?
