Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8"

Sirs,

1.We need both named parameters implemented through map and= , also varags if we want to call with different numbers of arguments= , here 25 as well as 24.

varag= s has the syntax

<= p class=3DMsoListParagraph>def foo(Object... args)=C2=A0 // same as def = foo(Object[] args)

= ;

2.As for . =E2=80=A6What we= 've discovered from testing is that if we send a value as either "true= " or "false", it acts as if we sent "true".&nb= sp;=E2=80=A6=C2=A0 for me it does not happen; I get the correct response as= below.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 de= f g(Map map){ println !map.one}=C2=A0 // I have complemented the pas= sed parameter ! map.one

=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 g(one:false)

<= p class=3DMsoNormal>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0 g(one:true)

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 The output is :

=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 true

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= false

Thanking you,

T.Rath= inavelu

Sent from Mail for Windows 10

From: MG
Sent: Sunday, April 26, 2020 5:00 AM
= To: users@groovy.apache.org<= /a>; David Karr
Sub= ject: Re: Strategy for optionally excluding a named method parameter?

Hi David,

since, as was mentioned, named = parameters are implemented as a map underneath in Groovy, you should be abl= e to remove the map entry of the parameter you do not want to pass, though = I did not try this myself...

Cheers,
mg

On 25/04/2020 20:57, David Karr wrote:

=
On Sat, Apr 25, 2020 at 2:00= AM Rathinavelu <rathinavelu@gm= ail.com> wrote:
Named parameters are not available in = Groovy, say, as in Python., though they say it is. Groovy has only mapped p= arameters. The earlier mail works for a single =E2=80=98named=E2=80=99 para= meter; if there are more parameters Groovy does not work as =E2=80=98expect= ed=E2=80=99; it treats them only as positional parameters.
Kindly= mail me an use-case.
T.Rathinavelu
<= div>

The code sample looks something like this:

= ;   functionName param1: value,
        param2: value,=
     &nb= sp; param3: value,
&nbs= p;       param4: value,
<= div>
        ...
     &n= bsp; param25: value

For instance, we need to = make either the previous call or the following:

    functionName param1: value,
<= p class=3DMsoNormal>        param2: valu= e,
    &n= bsp;   param3: value,
&n= bsp;       ...
        param25: value=

<= p class=3DMsoNormal>Where the "param4" key and value are not prov= ided. Presently, we have an "if" checking for a condition, = followed by the "true" block with the first version of the functi= on call with 25 parameters, followed by the "else" and the "= false" block with the second version, which has 24 parameters, all the= same values as in the first block, except for the one key and value not pr= ovided in the second version.

Sent from Mail for Win= dows 10

From: David Karr
Sent: Satu= rday, April 25, 2020 1:48 AM
To: users@groovy.apache.org
Subject: Strategy for optionally excluding a named method parameter?

Lately my only Groovy work is scripted pi= pelines in Jenkins, version 2.89.4 .

<= div>
I'm working with an api that is somewhat dumb in one respect.&nb= sp; The method we call takes ~25 parameters. We send them as named pa= rameters. One of the parameters is of boolean type. What we've discov= ered from testing is that if we send a value as either "true" or = "false", it acts as if we sent "true". If we cons= truct the call without that parameter entirely, it acts as if we sent "= ;false". I tried making it send null, but that just causes it to fail = at runtime. We presently have an "if" for that one flag, wi= th two calls to the method, one taking 25 parameters, the other taking 24.&= nbsp; It is really obnoxious.

Obviously, the proper fix is to change their api so that it works corre= ctly. The reality is, that's not going to happen any time soon in geo= logical terms.

Is there a = concise groovy syntax we could use that would optionally include or exclude= a single parameter to the method?