[Top][All Lists]

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

Re: Octave's and Matlab's limitations

From: Jordi Gutiérrez Hermoso
Subject: Re: Octave's and Matlab's limitations
Date: Thu, 22 Nov 2012 08:39:06 -0500

On 22 November 2012 04:49, Francesco Potortì <address@hidden> wrote:
>>Though I agree with you that typically more than one language is
>>necessary, there is _nothing_ Matlab/Octave can do and other language
>>can't with the same ease or even easier and more elegantly and less
> I think that the winning feature of Octave is the index notation and the
> ease to access submatrices with a readable and intuitive syntax.  That
> is, what is known as the Matlab index notation.  Are there any other
> languages that allow such indexing power and clarity?

Numpy's indexing is essentially the same except it's 0-based to
conform to general Python usage. Numpy can't extend the Python
language beyond what Python itself allows, though, so things like [A;
B] to concatenate matrices in Octave become np.vertcat([A, B]) or
something like that, can't exactly remember. I don't think this is a
huge loss, however.

There is nothing all that magical about Octave indexing.

- Jordi G. H.

reply via email to

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