[Top][All Lists]

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

[Octave-bug-tracker] [bug #32924] lcm does not warn when losing precisio

From: Nicholas Jankowski
Subject: [Octave-bug-tracker] [bug #32924] lcm does not warn when losing precision
Date: Sat, 23 Mar 2019 23:47:57 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Edge/16.16299

Follow-up Comment #24, bug #32924 (project octave):

adding that (a) this still appears to be valid in 5.1.0, as no warnings are
generated by lcm

(b) lcm appears to no longer(?) accept input as given in the example. I
couldn't find an example of matlab lcm accepting input that way either, except
as a shadowed lcm in the symbolic toolbox.

Matlab 2018b:

>> lcm([26:52])
Not enough input arguments.

>> lcm(num2cell(26:52){:})
Error: ()-indexing must appear last in an index expression.
>> a = num2cell(26:52);
>> lcm(a{:})
Error using lcm
Too many input arguments.

Octave 5.1.0

>> lcm([26:52])
error: Invalid call to lcm.  Correct usage is:
 -- lcm (X, Y)
 -- lcm (X, Y, ...)

>> lcm(num2cell([26:52]){:})
ans =    2.3971e+25

>> lcm(num2cell([52:-1:26]){:})
ans =    1.1213e+30

>> lcm(num2cell(25:52){:})
ans =    1.1866e+28

so, it's still here, but I can't recreate it in matlab to know if that exact
situation still produces an error/warning.


Reply to this item at:


  Message sent via Savannah

reply via email to

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