Re: [Scilab-users] {EXT} Re: display of complex/not real numbers, again

Stéphane, Let me give the following rationale. When parsing with msscanf we get --> msscanf("1.60009","%lf")==1.6  ans  =   T but --> msscanf("1.70018","%lf")==1.7  ans  =   F The actual display algorithm does not use msscanf but a cross-platform code (msscanf

Re: [Scilab-users] {EXT} Re: display of complex/not real numbers, again

Le 17/09/2019 à 15:33, Stéphane Mottelet a écrit : Le 17/09/2019 à 15:20, Federico Miyara a écrit : Dear all, I think that saying that 1.70018 should be represented as 1.700 and that representing it as 1.7 instead is dishonest seems a bit too much for me. What about

Re: [Scilab-users] {EXT} Re: display of complex/not real numbers, again

Le 17/09/2019 à 15:20, Federico Miyara a écrit : Dear all, I think that saying that 1.70018 should be represented as 1.700 and that representing it as 1.7 instead is dishonest seems a bit too much for me. What about 1.712345649? With the available decimal

Re: [Scilab-users] Generating a boolean vector or matrix

Stéphane, I hope no. These are typical -- IMO fake -- functions that i would not expect in Scilab (and in any other language). There are many trivial and fast ways to create a boolean array of given dimensions. true(m,n) may be fake if, as in other message has been clarified, boolean

Re: [Scilab-users] display of complex/not real numbers, again

Le 17/09/2019 à 15:19, Federico Miyara a écrit : Stéphane, --> x=1:0.1:2  x  =    1.   1.1   1.2   1.3   1.4   1.5   1.6   1.700   1.8 1.9   2. nothing triggers it in actual Scilab version. This was just an example of what could be displayed after the patch I propose (in its last

Re: [Scilab-users] {EXT} Re: display of complex/not real numbers, again

Dear all, I think that saying that 1.70018 should be represented as 1.700 and that representing it as 1.7 instead is dishonest seems a bit too much for me. What about 1.712345649? With the available decimal places you would represent it as 1.7123456 Wouldn't

Re: [Scilab-users] display of complex/not real numbers, again

Stéphane, --> x=1:0.1:2  x  =    1.   1.1   1.2   1.3   1.4   1.5   1.6   1.700   1.8 1.9   2. However I get this:   > x=1:0.1:2  x  =    1.   1.1   1.2   1.3   1.4   1.5   1.6   1.7   1.8   1.9   2. But it is true that x(7) - 1.7 yields 2.220D-16. Here there are two problems, an

Re: [Scilab-users] xload mess ...

Le 16/09/2019 à 11:31, Antoine Monmayrant a écrit : Le 13/09/2019 à 13:38, Samuel Gougeon a écrit : Hello Antoine, Hello Samuel, As discussed with you there , xload() has been restored and upgraded for Scilab 6.0.2. However, its help