octave-maintainers
[
Top
][
All Lists
]
Advanced
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
Why a separate isequal?
From
:
David Spies
Subject
:
Why a separate isequal?
Date
:
Sun, 9 Mar 2014 21:03:55 -0600
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?
reply via email to
[Prev in Thread]
Current Thread
[
Next in Thread
]
Why a separate isequal?
,
David Spies
<=
Re: Why a separate isequal?
,
Daniel J Sebald
,
2014/03/09
Re: Why a separate isequal?
,
Richard Crozier
,
2014/03/10
Prev by Date:
Re: New Geodesy functions to Mapping Package
Next by Date:
Re: Octave 3.8.1 Released
Previous by thread:
close down savannah patches?
Next by thread:
Re: Why a separate isequal?
Index(es):
Date
Thread