Re: [Scilab-users] On parameters passing by name in scilab functions

2017-02-27 Thread tim
On 2017-02-27 11:18, Samuel Gougeon wrote: Le 27/02/2017 à 19:49, Tim Wescott a écrit : You misread my comments. Tim _likes_ named parameters. If Tim were on the C++ standards committee (which is as likely as pigs flying, BTW) Tim would agitate that named parameters be adopted into that langu

Re: [Scilab-users] On parameters passing by name in scilab functions

2017-02-27 Thread Samuel Gougeon
Adelson, It could somewhat misleading to get conclusions about Scilab behavior with named parameters out of the current fft() behavior, because there are some pending bugs about fft(), independently from named arguments. IMHO, it would be safer to do tests about named arguments with another

Re: [Scilab-users] On parameters passing by name in scilab functions

2017-02-27 Thread Adelson Oliveira
BTW, Scilab has always had problems to provide interfaces to languages that accept optional parameters (but not only because of it) like modern FORTRAN. 2017-02-27 18:57 GMT-03:00 Adelson Oliveira : > Well, now scilab 6.0 ignores named parameters at fft calls. One can check > it with > > fft(eye

Re: [Scilab-users] On parameters passing by name in scilab functions

2017-02-27 Thread Adelson Oliveira
Well, now scilab 6.0 ignores named parameters at fft calls. One can check it with fft(eye(4,4),-1,dims=4,incr=1)-fft(eye(4,4),-1) the result is 4X4 matrix with zeros. This is different from (without names): fft(eye(4,4),-1,4,1)-fft(eye(4,4),-1). Then, I guess it is to say optional parameters ar

Re: [Scilab-users] On parameters passing by name in scilab functions

2017-02-27 Thread Samuel Gougeon
Le 27/02/2017 à 19:49, Tim Wescott a écrit : You misread my comments. Tim _likes_ named parameters. If Tim were on the C++ standards committee (which is as likely as pigs flying, BTW) Tim would agitate that named parameters be adopted into that language. Scilab, Verilog, and (I think) VHDL ha

Re: [Scilab-users] On parameters passing by name in scilab functions

2017-02-27 Thread Samuel Gougeon
Le 27/02/2017 à 19:36, Samuel Gougeon a écrit : .../... So, Tim is right. Calls with named parameters make the code fragile, or make somewhat harder to code the analysis of input arguments in a robust way. /This coding way still increases functions overheads, that make them slower./ Hmmm, ac

Re: [Scilab-users] On parameters passing by name in scilab functions

2017-02-27 Thread Tim Wescott
You misread my comments.  Tim _likes_ named parameters.  If Tim were on the C++ standards committee (which is as likely as pigs flying, BTW) Tim would agitate that named parameters be adopted into that language.  Scilab, Verilog, and (I think) VHDL have it, and particularly in a language that allow

Re: [Scilab-users] On parameters passing by name in scilab functions

2017-02-27 Thread Samuel Gougeon
Hello Adelson, Le 27/02/2017 à 15:46, Adelson Oliveira a écrit : Hi, Let's take fft as an example. In scilab 5 one could call fft specifying parameters like dim and incr by name, fft(A,-1,dim=100,incr=1) Here names are simply ignored. There would be a true call by names if the order would

Re: [Scilab-users] On parameters passing by name in scilab functions

2017-02-27 Thread Tim Wescott
Is this true?  Parameter passing by name is hugely useful -- they'd have to re-write a whole bunch of libraries to make it work, and I'd have a lot of stuff that would be instantly obsolete. On Mon, 2017-02-27 at 11:46 -0300, Adelson Oliveira wrote: > Hi, > > Let's take fft as an example. > > In

[Scilab-users] On parameters passing by name in scilab functions

2017-02-27 Thread Adelson Oliveira
Hi, Let's take fft as an example. In scilab 5 one could call fft specifying parameters like dim and incr by name, fft(A,-1,dim=100,incr=1) Codes that used to work in scilab 5 now gives wrong results (no error messages!) in scilab 6 because the new release ignores named parameters. To get expect