|
From: | Daniel J Sebald |
Subject: | Re: Why a separate isequal? |
Date: | Sun, 09 Mar 2014 22:49:16 -0500 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111108 Fedora/3.1.16-1.fc14 Thunderbird/3.1.16 |
On 03/09/2014 10:03 PM, David Spies wrote:
I noticed that: octave:1> isequal(1,2) ans = 1 I'm guessing this is a bug. Nonetheless, why is there even a separate isequal function? Why can't it just be defined as function [res] = isequal(a,b) res = (a == b) endfunction Are there types for which it's meant to differ from ==? Is this supposed to be used for some sort of test?
According to the documentation, isequal accepts a general tuple:
isequal(5,5,5)
ans = 1
5 == 5 == 5
ans = 0Why it is failing on your system is a good question. Seems like a basic function that shouldn't have changed much.
What does
test isequal
PASSES 23 out of 23 tests produce for you? Dan
[Prev in Thread] | Current Thread | [Next in Thread] |