I thought I was doing the following correctly, and maybe it=92s a bug or maybe it=92s just a logic problem on my end (I am still very new to Lasso 9). I searched for any references to this problem, but didn=92t see any.

With the following code as example:

define test(a::integer, b::integer=0, -c::integer=0) => {
local(d) = =91result -> a=' + #a + ' b=' + #b + ' c=' + #c
return(#d)
}

I get the following responses (code an then result):
[test(1,2,-c=3)]
result -> a=1 b=2 c=3

[test(1,-c=2)]
result -> a=1 b=c:2 c
From the documentation, the order of these should be required, then optional, then keyword. I=92m not sure where I=92m going wrong on this one? The optional parameter in the 2nd example should be 0, but instead it is taking the keyword parameter and passing it into the optional parameter.

Steve


#############################################################
This message is sent to you because you are subscribed to
the mailing list Lasso Lasso@lists.lassosoft.com
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <Lasso-unsubscribe@lists.lassosoft.com>
Send administrative queries to <Lasso-request@lists.lassosoft.com>