Re: Matlab compatibility of assert

[John W. Eaton]

On 09/24/2013 01:28 PM, Rik wrote:

> How bothersome!  We have a perfectly good feature and then the syntax gets
> changed underneath us.

Yes, it's what we get for innovation.

> I guess it's fine to change the function.  I would rather see oassert for
> Octave assert rather than tassert.  This follows the pattern for ostrsplit
> and strsplit where the same pre-existing function situation happened and we
> had to change Octave to accommodate Matlab.

OK, I don't have any particular attachment to the name, so oassert is
fine with me, though when I see that, I think "old assert", not
"octave assert".

If we had packages, could that help here?  Then we could add something
like

  import octave.test.*

in the test function and ensure that we get the version of assert that
we want without having to change any of the existing test code.

If that would help, then I think we could put this change off until
later.  It hasn't really caused trouble for us so far, so maybe we
should wait.

jwe